[GH-ISSUE #459] Host noVNC over the same port as django interface port. #341

New issue

Open

opened 2026-02-27 16:38:56 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 16:38:56 +03:00

Owner

Originally created by @crocket on GitHub (Oct 14, 2014).
Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/459

If I launch noVNC from a remote machine but have no access to the port 6080, I can't use noVNC.

Isn't it possible to have the django web interface port serve as a websocket port, too?

In my company, an HTTP/HTTPS apache httpd reverse proxy is in front of every web service, so it's beneficial to use only one port for django web interface and websocket.

Originally created by @crocket on GitHub (Oct 14, 2014). Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/459 If I launch noVNC from a remote machine but have no access to the port 6080, I can't use noVNC. Isn't it possible to have the django web interface port serve as a websocket port, too? In my company, an HTTP/HTTPS apache httpd reverse proxy is in front of every web service, so it's beneficial to use only one port for django web interface and websocket.

kerem commented

2026-02-27 16:38:57 +03:00

Author

Owner

@crocket commented on GitHub (Oct 14, 2014):

https://github.com/jrief/django-websocket-redis could help.

@crocket commented on GitHub (Oct 14, 2014): https://github.com/jrief/django-websocket-redis could help.