ProxMox CLI/API (VNC Port not open)

[JaXnPrivate]

If I first request a VNC proxy and then a WebSocket via the Proxmox API, regardless of whether JSON or CLI, the port is not online/open on the server.

Is there anything I need to be aware of with Creation, or can I debug it somehow?

pvesh create /nodes/homeserver/qemu/100/vncproxy -websocket true

Returns a port (5900) with cert, user, ticket...

pvesh get /nodes/homeserver/qemu/100/vncwebsocket -port 5900 -vncticket

Returns the same port (5900)...


Telnet shows that the VNC is not online/open.

telnet localhost 5900
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused

 

[JaXnPrivate]

I checked the syslog and the session seems to time out shortly after creation.

I don't know if this is normal (security based) or maybe the proxy could not be started, I can access it via Vanilla VNC if I am fast, only VNC Websocket just doesn't work.

2024-02-29T16:07:35.528888+01:00 homeserver pvedaemon[204700]: <root@pam> starting task UPID:homeserver:00044556:007508C5:65E09DB7:vncproxy:100:root@pam:
2024-02-29T16:07:35.530665+01:00 homeserver pvedaemon[279894]: starting vnc proxy UPID:homeserver:00044556:007508C5:65E09DB7:vncproxy:100:root@pam:
2024-02-29T16:07:45.530532+01:00 homeserver pvedaemon[279894]: connection timed out
2024-02-29T16:07:45.544956+01:00 homeserver pvedaemon[204700]: <root@pam> end task UPID:homeserver:00044556:007508C5:65E09DB7:vncproxy:100:root@pam: connection timed out


When creating WebSocket via API:
2024-02-29T16:15:24.869824+01:00 homeserver pvedaemon[281608]: starting vnc proxy UPID:homeserver:00044C08:0075C01B:65E09F8C:vncproxy:100:root@pam:
2024-02-29T16:15:24.870097+01:00 homeserver pvedaemon[281020]: <root@pam> starting task UPID:homeserver:00044C08:0075C01B:65E09F8C:vncproxy:100:root@pam:
2024-02-29T16:15:27.767868+01:00 homeserver pvedaemon[281020]: <root@pam> end task UPID:homeserver:00044C08:0075C01B:65E09F8C:vncproxy:100:root@pam: OK

 

[JaXnPrivate]

Everything that is written here in the forum about the VNC proxy is very unclear.

The fact is that with vncwebsocket only a forwarding header is "activated".

This means that the PVECookie must be included... But no 0815 user should receive it, that's why I simply wrote a reverse proxy in Java...

Vanilla VNC Server <--> WebSocket Server <--> NoVNC.