This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Clientless Access VPN - BUG

Hi,

I have an internal website that my external workers have been accessing via the portal (VPN > Clientless Access). As of yesterday my remote workers can't access pages correctly. I've restarted Sophos XG and the Server. I've noticed in the Log Viewer the following...

Log Comp: SSL VPN

Status: ALLOWED

Username: My Username

Message: Use "My Username" was allowed access of the HTTP resource http://images/logo.jpg

Is this correct? Does the IP address of the internal server need to be prefixed? Eg. http://10.12.44.10/images/logo.jpg

The portal website sometimes displays the page poorly or not at all and I can see the following source code...

The URL for this blank white page is  = https://myexternalip/userportal/CRSSL/http/ClientLogin.aspx

The source code for that page is...

"<!--#set var="TITLE" value="SSLVPN User Portal Error:"

--><!--#include virtual="include/top.html" -->


<!--#if expr="$REDIRECT_ERROR_NOTES" -->
<!--#include virtual="include/spacer.html" -->
<!--#echo encoding="none" var="REDIRECT_ERROR_NOTES" -->
<!--#endif -->"

Please can you help or throw any suggestions my way? Many thanks

EDIT: The first page kind of works. There's no neat formatting or styling. However I can see text. The URL displays the following...

https://externalip/userportal/CRSSL/http/10.12.44.10:8181

When I click any link, a white page appears and the URL changes to https://externalip/userportal/CRSSL/pagename.aspx

It's not prefixing the URL and therefore nothing is displaying correctly. Please can others check this to see if it's just me :)

Many thanks



This thread was automatically locked due to age.
Parents Reply
  • Ok about priorities, but these bugs means they just didn't even tried a single html page with ANY js/css/image

    <html>

    <body>

    <img src="logo.png">

    </body>

    </html>

     

    That's it... And these known issues are around since 15.1, I'm not talking 2-3 weeks...

    Even worst is the support which took 1 week only to connect via logmein to my PC because they want to see the issue (and I must add they don't want to spend 1 minute to replicate it on their labs) and after I recreated from ground up the whole issue the support told me that clientless for http(s) "apparently" does not work and to just use a SSL VPN...

Children