-
Notifications
You must be signed in to change notification settings - Fork 820
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 Long lived websocket seems to disconnect consistently #1282
Comments
This is actually not a bug, rather a limitation of the current production websocket impl, you can contact support and ask them to enable the Websocket handoff feature which can increase the lifetime of a websocket connection by an order of magnitude. the drawback of this is lesser visibility (you are unable to view total bandwidth of websockets in the zone) |
Is this the reason? Any plans this will change? (soon ?) Unless its something on my end sometimes its reconnecting every other minute which kinda makes it hard to make it unnoticed |
I don't work at cf and can't comment about any plans that may or may not exist but you can ask support to enable websocket handover |
every other minute is quite often, Id think there is something else going on, possibly config somewhere. consider asking support or posting in discord/forums |
Its mostly fine but yes some days theres very "hot" 10 minutes of reconnects. Also find it hard to believe this is expected but only does it through the tunnel and at specific times of the day so |
Describe the bug and To Reproduce
A service is being exposed via a cloudflared tunnel (http endpoint).
Clients connect to the service via the exposed tunnel which then upgrades the connection to a websocket.
The clients consistently disconnect - and a successful reconnect happens since our clients can reconnect.
Expected behavior
This only happens when the client connects via the tunnel, if no tunnel is being used the disconnect behavior does not happen.
Environment and versions
Logs and errors
When the socket disconnects we do get this output:
Read error: websocket: close 1006 (abnormal closure): unexpected EOF
The text was updated successfully, but these errors were encountered: