[GH-ISSUE #500] https via nginx breaks VNC Console #370

Open
opened 2026-02-27 16:39:03 +03:00 by kerem · 2 comments
Owner

Originally created by @seitzbg on GitHub (Feb 13, 2015).
Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/500

Can you please describe how to make the VNC console work again if using HTTPS to access webvirtmgr's interface? I tried the 'hacks' setting 'encrypted': false for console-vnc in templates but this did not resolve my issue.

Great app and thanks in advance!

Originally created by @seitzbg on GitHub (Feb 13, 2015). Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/500 Can you please describe how to make the VNC console work again if using HTTPS to access webvirtmgr's interface? I tried the 'hacks' setting 'encrypted': false for console-vnc in templates but this did not resolve my issue. Great app and thanks in advance!
Author
Owner

@brenard commented on GitHub (Feb 13, 2015):

If you access to webVirtMgr using https, the console will be access using encrypted connection but by default, webvirtmgr-console script use a bad cert file to make connection encrypted possible. You have to add WS_CERT variable in webvirtmgr/local/local_settings.py file : The value of this variable have to be the full path of a certificate file in PEM format including key and cert. You could use the same certifcate as you using in Nginx configuration.

<!-- gh-comment-id:74250513 --> @brenard commented on GitHub (Feb 13, 2015): If you access to webVirtMgr using https, the console will be access using encrypted connection but by default, webvirtmgr-console script use a bad cert file to make connection encrypted possible. You have to add WS_CERT variable in webvirtmgr/local/local_settings.py file : The value of this variable have to be the full path of a certificate file in PEM format including key and cert. You could use the same certifcate as you using in Nginx configuration.
Author
Owner

@sammcj commented on GitHub (Feb 27, 2015):

It would be nice to have that WS_CERT variable exposed to the config - how hard would that be to do?

<!-- gh-comment-id:76364309 --> @sammcj commented on GitHub (Feb 27, 2015): It would be nice to have that WS_CERT variable exposed to the config - how hard would that be to do?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/webvirtmgr#370
No description provided.