mirror of
https://github.com/retspen/webvirtcloud.git
synced 2026-04-25 15:35:57 +03:00
[GH-ISSUE #126] Support Websocket proxying #83
Labels
No labels
bug
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/webvirtcloud#83
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @saivert on GitHub (Aug 10, 2016).
Original GitHub issue: https://github.com/retspen/webvirtcloud/issues/126
Current setup requires having websockify listening on port 6080.
It should be possible to have nginx also proxy websocket traffic via port 80 on alternate path (e.g http://webvirtmgr.example.com/novncd/) otherwise people are required to open up access to port 6080 in their firewalls and expose this to the world.
Edit: I have this working using a tiny change. It requires splitting up the WS_HOST/WS_PORT settings in two parts. One for the novncd process to know where to listen and one that the web vnc/spice client connects to.
Then appropriate nginx config directives must be added.
And the nginx config:
@forumi0721 commented on GitHub (Nov 16, 2016):
good for me
thanks
@fengqi commented on GitHub (Mar 20, 2017):
It seems that the latest version can't work
@zingmars commented on GitHub (Jun 6, 2018):
The patch sort-of worked for me. The problem is that the novncd daemon thinks that you're trying to use a file socket over network because of some really odd logic, so it wouldn't work. I suppose deleting the whole section would work, but it makes for a way smaller patch file to just change the offending check.
@skywind3000 commented on GitHub (Nov 5, 2018):
@retspen why not include this patch for out-of-box https support ?
@lord-kyron commented on GitHub (Nov 5, 2018):
@skywind3000 I have implemented this patch in my version of the repo. You can try it:
https://github.com/Bandic007/webvirtcloud-plus.git
@skywind3000 commented on GitHub (Nov 6, 2018):
btw: @Bandic007 , the vnc port is hardcode to 6080, but what if the port is not 6080 ? eg, two vnc console is active at the same time, they must be allocated to different ports.
@lord-kyron commented on GitHub (Nov 6, 2018):
@skywind3000 - there is no problem about this. That is why VNC is using tokens to assure different vnc consoles will work. Actually 6080 is the port on the server on which vnc server is accepting connections, not the port of the vm itself for vnc.