topic Re: Clientless VPN not displaying page content when using any browser in General Topics

Clientless VPN not displaying page content when using any browser

PaulMoore — Wed, 08 Apr 2020 15:05:25 GMT

Hi,

We have set up a clientless VPN trying to access a server with AIV Hub on it (this provides a customer portal). The VPN works fine and we can log in and see the application.

The URL for the application is http tcp port 8080 so it has been written as http://x.x.x.x:8080/aiv

If I click on the app a new browser tab opens but the page does not load (the tab does display the AIV icon however). This is the same regardless of which browser I try (IE 11, Edge 44, Chrome 80, Firefox 75)

I have carried out a tcpdump on the AIV server and can see traffic reaching it on port 8080 using a source IP address of the firewall egress interface local to the server.

Is there anything else needed when using a using a different port like 8080 or can anyone shed any light on what may or may not be happening?

Many thanks.

Paul.

Re: Clientless VPN not displaying page content when using any browser

BPry — Wed, 08 Apr 2020 17:49:31 GMT

@PaulMoore ,

You're going to need to ensure that you have a security policy that is actually accounting for the non-standard port access instead of attempting to utilize application-default.

Re: Clientless VPN not displaying page content when using any browser

PaulMoore — Thu, 09 Apr 2020 07:45:34 GMT

@BPry

Thanks for replying. We have the service-http group applied and this includes 8080. I can see packets hitting the server on this port so it suggests the security policy is working.

Cheers.

Paul.

Re: Clientless VPN not displaying page content when using any browser

PaulMoore — Fri, 17 Apr 2020 10:47:39 GMT

Re: Clientless VPN not displaying page content when using any browser

NavidAlam — Wed, 20 Jan 2021 11:57:31 GMT

I have upgrade from 8.0.12 to 9.0.11 Before it was working now it is not . I can login to Webpage but many things are missing including data logs . Can any one tell me this bug is fix or i had to down grade to 8.0.12 ?