Forum

SignalR WebSocket f...
 
Notifications
Clear all

SignalR WebSocket fails through Skudonet 7.2.1 – “connection not found on the server” even after cookie-based persistence & WebSocket-enabled farm

2 Posts
2 Users
0 Reactions
97 Views
(@kajun1337)
New Member
Joined: 1 month ago
Posts: 1
Topic starter  

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

# Persistence
  Mode .................... IP: Client address
  Session TTL ............. 1800 s
 
# Advanced
  Rewrite location headers  Enabled
  HTTP verbs accepted ..... + MS RPC extensions verbs
  100-Continue mode ....... Ignore
 
  Backend connection timeout  300 s
  Backend response timeout    300 s
  Client request timeout      300 s
  Frequency to check resurrected back-ends  21 s

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?


   
Quote
emiliocm
(@emiliocm)
SKUDONET Engineer Moderator
Joined: 8 months ago
Posts: 52
 

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!

 


   
ReplyQuote
Share:

Download Skudonet ADC Load Balancer
Community Edition

Source Code

A versatile and installable ADC system designed for diverse vendor hardware.

DOWNLOAD SOURCE

Installable ISO 

Load Balancing as a Service alongside an ADC orchestration toolkit.

DOWNLOAD ISO
Download Community Edition

Download Community Edition

“We manage the information you provide with the sole aim of assisting with your requests or queries in regards to our products or services; applying the computer and security procedures to ensure its protection. Your data can be rectified or removed upon request but won’t be offered to any third parties, unless we are legally required to do so.” Responsible: SKUDONET SL - info@skudonet.com