1
0
Fork 0
mirror of https://github.com/retspen/webvirtcloud synced 2026-11-09 11:46:49 +00:00
webvirtcloud/conf/runit
catborise 68b104dfe4 feat(console): the VNC console uses the panel's own address
The console pages connect to /novncd/ on the address, scheme and port the
page itself was loaded from; nginx proxies it to novncd, which listens on
the loopback only. There is nothing to configure: the console works on
HTTPS (wss), behind another proxy and on any published port.

Before, the page connected to WS_PUBLIC_HOST/PORT/PATH, port 6080 by
default: straight to novncd, past nginx and without TLS, so an HTTPS panel
and a Docker container published on another port had no console until the
public port was set by hand, and novncd listened on every interface.

Gone: WS_PUBLIC_PORT, WS_PUBLIC_HOST, WS_PUBLIC_PATH and WS_CERT, the
installer's two public console questions and its 6080 firewall rule, the
Docker image's WS_PUBLIC_PORT and its init script lines, the manual
install's firewall rule for 6080 and nginx's unused /websockify location.
WS_HOST defaults to 127.0.0.1. A VM with a QEMU websocket port is still
reached on that port of the panel's host name (left for a separate
decision).
2026-10-26 20:14:04 +03:00
..
10_webvirtcloud_init.sh feat(console): the VNC console uses the panel's own address 2026-10-26 20:14:04 +03:00
nginx Dockerization 2015-10-15 20:47:10 +08:00
nginx-log-forwarder Dockerization 2015-10-15 20:47:10 +08:00
novncd.sh build: systemd runs the panel on hosts instead of supervisor 2026-10-17 23:18:26 +03:00
secret_generator.py update secret generator with new python secrets module - urlsafe 2022-06-28 11:13:23 +03:00
socketiod.sh feat(console): a working serial console 2026-10-17 19:43:09 +03:00
webvirtcloud-worker.sh build: run the job worker in every install type 2026-10-14 23:27:57 +03:00
webvirtcloud.sh fix linter errors: bash scripts 2020-10-17 23:30:00 +03:00