You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our frontend application is moving to replace inhouse websocket server with NATS Websocket. All seems good except the nats websocket connection is randomly getting closed and a new one is created. In firefox the error code mentioned is Closed 1006. pingInterval is set to 25 seconds to keep the connection from idling but i noticed in some instances a ping is sent after a whole minute, thus browser closes the connection.
You can notice the last ping sent after 60 second after which the connection is closed by the browser,
Expected behavior
Nats websocket connection should remain open and pings should be sent consistently
3 node nats cluster runs in Kubernetes behind an AWS NLB.
TLS is terminated by APISIX gateway route.
Socket endpoint is wss://
Client runs in the browser.
Observed behavior
Our frontend application is moving to replace inhouse websocket server with NATS Websocket. All seems good except the nats websocket connection is randomly getting closed and a new one is created. In firefox the error code mentioned is
Closed 1006
.pingInterval
is set to 25 seconds to keep the connection from idling but i noticed in some instances a ping is sent after a whole minute, thus browser closes the connection.You can notice the last ping sent after 60 second after which the connection is closed by the browser,
Expected behavior
Nats websocket connection should remain open and pings should be sent consistently
Server and client version
nats-server:
v2.10.22
nats.ws:
v1.29.2
Browsers tested:
Chrome
,Firefox
,Safari
Host environment
3 node nats cluster runs in Kubernetes behind an AWS NLB.
TLS is terminated by APISIX gateway route.
Socket endpoint is
wss://
Client runs in the browser.
Steps to reproduce
The text was updated successfully, but these errors were encountered: