-
Notifications
You must be signed in to change notification settings - Fork 65
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
Inactive NoVNC session disconnected by network appliance #23
Comments
@patlachance Thanks for the idea. I'll look at it. |
Hello @patlachance would you please test the new image with the hearbeat? I do not have an appropriate environment at the moment. You can find the updated image accetto/ubuntu-vnc-xfce-g3:dev-heartbeat on Docker Hub. I've also published a temporary branch next-release on Git Hub. The CHANGELOG describes the changes. Note that the README files are not completely updated yet. You should set the new environment variable NOVNC_HEARTBEAT by creating the container, like
If starting with the parameter
Please let me know, if it really helps. Thanks. Regards |
That's really funny. I've just found, that I've completely missed you PR! So much about doing too many things at once. I'll check your PR now and you can test my changes in a meantime. :) |
@patlachance Can you confirm that it's really helping? Have you tested it? |
@accetto sorry for the delay. Yes the image works as expected. |
As a user of this image behind network appliance (load-balancer, reverse proxy, ...)
I should have an option to enable websocket ping/pong
In order to avoid being disconnected by the network appliance dropping the inactive TCP session.
Network appliance (load-balancers, reverse proxy) are configured to drop inactive sessions. For example, nginx default configuration is 60 seconds. Same for AWS ELB Classic load balancer, which can be increased up to 3600 seconds.
Websocket provide a configurable ping/pong mechanism to maintain tcp sessions opened on each network hops using heartbeat packet. And there is novnc_proxy parameter to enable it.
The text was updated successfully, but these errors were encountered: