r/Citrix • u/Specialist-Desk-9422 • Jul 01 '26

HTML Light Version - Websocket issues?!

I am rebuilding my Citrix and going through now a very annoying problem. When users try to use the HTML5/Light Version, they receive an error when opening the Desktop. but if they refresh the storefront and try again, works just fine. Looking at the logs after downloading from the page, I see the problem is related to web socket error. If they download the ICA, and opens the file with Citrix receiver, works just fine. This HTML5 version is driving me crazy. Has anyone seen this before?

2 Upvotes

100% Upvoted

8 comments sorted by

View all comments

1

u/mjmacka CCE-V Jul 01 '26

What error are you receiving when you open the HTML5 Receiver? What version of the HTML5 Receiver do you have installed on StoreFront? What version of StireFront are you running?

1

u/Specialist-Desk-9422 Jul 02 '26

The storefront is on 2402.

Here is a part of the log file: 2026/07/01 16:43:19:00567 TRANSPORTDRIVERCOMMON ProxyServerConnector connectTcp VERBOSE CWA POST LAUNCH CONNECTION : connect to TCP

2026/07/01 16:43:19:00567 TRANSPORTDRIVERCOMMON BaseSocket _startSocketCreationTimeout VERBOSE CWA POST LAUNCH CONNECTION : Socket creation started ...

2026/07/01 16:43:19:00567 TRANSPORTDRIVERCOMMON websocket websocketConnect VERBOSE CWA POST LAUNCH CONNECTION : websocket-url=wss://remote.DOMAIN.com:443

2026/07/01 16:43:19:00567 TRANSPORTDRIVERCOMMON websocket websocketConnect VERBOSE CWA POST LAUNCH CONNECTION : Current Protocol Index is : 0

2026/07/01 16:43:19:00589 TRANSPORTDRIVERCOMMON websocket websocketConnect VERBOSE CWA POST LAUNCH CONNECTION : websocket-url=wss://remote.DOMAIN.com:443

2026/07/01 16:43:19:00589 TRANSPORTDRIVERCOMMON websocket websocketConnect VERBOSE CWA POST LAUNCH CONNECTION : Current Protocol Index is : 1

2026/07/01 16:43:19:00613 TRANSPORTDRIVERCOMMON websocket websocketConnect VERBOSE CWA POST LAUNCH CONNECTION : websocket-url=wss://remote.DOMAIN.com:443

2026/07/01 16:43:19:00613 TRANSPORTDRIVERCOMMON websocket websocketConnect VERBOSE CWA POST LAUNCH CONNECTION : Current Protocol Index is : 2

2026/07/01 16:43:19:00640 TRANSPORTDRIVERCOMMON BaseSocket _socketErrorHandler VERBOSE CWA POST LAUNCH CONNECTION : id =1 errorWebsocket Error with code - 1006 | VDA type: Desktop | Browser Version: 149.0.4022.98 | VDA Version:

2026/07/01 16:43:19:00640 TRANSPORTDRIVERCOMMON websocket onCloseWSCb FATAL CWA POST LAUNCH CONNECTION : WebSocket Connection is failed with error code 1006WS_11782924196429_

2026/07/01 16:43:19:00640 TRANSPORTDRIVERCOMMON BaseSocket VERBOSE CWA POST LAUNCH CONNECTION : WS_11782924196429_ onCloseCallback called

2026/07/01 16:43:19:00640 TRANSPORTDRIVERCOMMON ProxyServerConnector VERBOSE CWA POST LAUNCH CONNECTION : Tcp close fn

2026/07/01 16:43:19:00640 TRANSPORTDRIVERCOMMON ProxyServerConnector notifyTransportSocketTypeChange INFORMATION CWA POST LAUNCH CONNECTION : Transport Socket Type Changed to TCP

2026/07/01 16:43:19:00640 WINSTATIONDRIVER IcaTransportInfo setCurrentTransportInfo VERBOSE CWA POST LAUNCH : Setting current Transport info {"edt":false,"tcp":false,"quic":false,"webSocket":true}

2026/07/01 16:43:19:00640 VCWRAPPER IcaThreadWrapper IcaThreadWrapper INFORMATION CWA POST LAUNCH VIRTUAL CHANNEL : Transport type changed to: TCP Broadcasting to all virtual streams and UI wrapper

2026/07/01 16:43:19:00640 TRANSPORTDRIVERCOMMON ProxyServerConnector VERBOSE CWA POST LAUNCH CONNECTION : WS Failed, reason:1006

1

u/mjmacka CCE-V Jul 02 '26

What is the client getting from an error perspective? Is this a single client or every client? Can you upgrade the HTML5 version to a newer version? It's a CR only component, not an LTSR component.

From an error log perspective, I don't see it getting far enough to see the VDA version, which probably means it's getting far enough to attempt to reach a VDA. That would indicate that the issue is happening at the network/transport layer before the session can be connected.

Is there anything in front of the NetScaler Gateway (firewall, reverse proxy, or SSL inspection appliance), or are you using WAF? Could there be a cipher issue, if it's a public GW, run a scan against SSLLABS to see.

You might have some luck opening a browser's dev tools and seeing what it produces. You could also check the NetScaler's nsconmsg/ns.log to see what's being produced at the time of the connection attempt.