Forum
I am running into a stubborn WebSocket issue with SignalR behind a Skudonet 7.2.1 appliance.
The browser console keeps showing like screenshot
Headers
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
Referrer-Policy: strict-origin-when-cross-origin
Content-Security-Policy-Report-Only: default-src 'self' https:; script-src 'self' 'unsafe-inline' https:; style-src 'self' 'unsafe-inline' 'unsafe-hashes'; img-src 'self' data: https:; connect-src 'self' https: wss:; object-src 'none'; base-uri 'self'; frame-ancestors 'none'
Permissions-Policy: accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=(), interest-cohort=(), browsing-topics=()
X-XSS-Protection: 1; mode=block
X-Permitted-Cross-Domain-Policies: none
Expect-CT: max-age=0, enforce
Are there additional CLI flags that must be enabled for WebSockets in version 7.2.1?
Anything else that can make Skudonet drop the Upgrade: websocket
request silently?
Good day, @kajun1337. Sorry for the late response.
In the attached screenshot, we see how the client establishes a connection to the load balancer using the WSS protocol. On the other hand, the Farm is configured for this service to use HTTP/S, so the issue here is that the Farm doesn't understand the WSS protocol. We encourage you to use WebSocket over HTTP(S). In this way, the HTTP traffic sends an upgrade header, allowing the FarFarm to communicate in WebSocket mode after the initial communication in HTTP(S) mode.
In case you can't start in HTTP(S) and upgrade to WebSocket, we encourage you to use L4XNAT instead.
Regards!