Hi Pulse Community,
we got an internal website we want to make available to some customers via WebSSL.
If I connect to my sign-in page and login I can see the website put parts of the website are still "loading".
We've tried to debug the websession as good as we can. If I connect to the website without Pulse I get a websocket which is about 300 bytes. If I do the same via Pulse I get a websocket but it's 0 bytes.
Are there special rewriting rules I need to add to use websockets via the Pulse gateway?
Thank you for your help.
From the debug output, do you see the websocket calls are being concatenated with the VPN server hostname separated a Danainfo keyword or still seeing the actual URL of the internal web application? For eg. https://<VPN hostname>/danainfo=<websocket calls>
Is it using WS or WSS schema for the websocket data? What is the HTTP response code you see for the 0 bytes response?
Does the web application loads after few minutes or is it stuck at 'loading' forever? Do you see any XHR calls being flown with URL format like https://<VPN hostname>/danainfo,/<webapp URL>,CT=xml after several 0 bytes of data?
What is the VPN server version?
as far as I can see the websocket calls and address which is not concatenated with the VPN server hostname.
It is not using WS or WSS and it seems I don't even get an HTTP response code.
The web application itself is stuck with loading forever and the XHR calls I can see in the debugger use the URL format you mentioned but with CT=sxml.
Can you try the setup using Passthrough proxy configuration and certainly, it might fix these issues. XML messages might be the fallback mechanism (XML HTTP Requests - XHR polling) used by your web application, in case if it's using NodeJs (can be disabled as well) or that might be normal XML data.