-
Notifications
You must be signed in to change notification settings - Fork 498
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Unify /websockify path used for vnc connections #2781
Milestone
Comments
Since it's working, I figure out that I needed to tweak a little the nginx timeouts. When you keep a fixed image (like a login screen), no packet pass and the noVNC client do not seems to send ping to maintain the connection, so nginx close the connection after a time (60s by default). I increase that to 15 minutes: location /websockify {
proxy_pass http://websocketproxy;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_send_timeout 15m;
proxy_read_timeout 15m;
} |
Evaluate in the context of the Sunstone revamp |
baby-gnu
added a commit
to baby-gnu/one-sunstone-rest-client
that referenced
this issue
Nov 27, 2019
As proposed in OpenNebula/one#2781 * README.md: describe the new “--ws-port” and “--ws-path” options * osc: add 2 options “--ws-port” and “--ws-path” to configure where is the NoVNC end point.
More context: #1034 (comment) |
noVNC to be fully deprecated in #5422 |
rsmontero
pushed a commit
that referenced
this issue
Nov 8, 2023
Modifies the way labels are displayed on vm templates
rsmontero
pushed a commit
that referenced
this issue
Mar 11, 2024
Modifies the way labels are displayed on vm templates (cherry picked from commit 5ca0180)
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Description
In continue to #878
Sunstone uses two different addresses for establish websocket connections with novnc.
If you call vnc console from the vm page, sunstone will call:
Unlike, if you click
, sunsone will call:
To Reproduce
Configure sunstone:
Configure nginx reverse-proxy, use config file from Enable path based NoVNC #878
Login to sunstone, and try to connect via vnc
Click
, and sunstone will successful establish vnc connection
Expected behavior
All connections will use
/websockify
path.Details
Additional context
I found working workaround, just specify missing path in
vnc_client_port
variable:Progress Status
The text was updated successfully, but these errors were encountered: