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
When the server restarts, a new JWT secret is issued. Thereby invalidating all issued access tokens. The socketio client is therefore rejected. This could be temporary fixed by setting a constant JWT secret, however this is not desirable in a production case.
Thus the server needs to send an event to the client that it should reauthenticate to obtain a new token and setup a new socketio channel
Describe the bug
I observed that nodes did not reconnect their websocket channel on a lost connection event.
In the node logs:
in the server logs:
To Reproduce
Steps to reproduce the behavior:
vdev start-demo-network
,vdev create-demo-network
vnode atttach
vserver stop
vserver start
,vserver attach
Details
The text was updated successfully, but these errors were encountered: