No access noVnc from external proxmox url

gdseb

Member
Sep 20, 2021
3
0
6
52
Hello,

I'am using proxmox version 7 (pve-manager/7.1-8/5b267f33). All is great but when i want to access VMConsole from external url (toto.prox.fr), i have a 'failed to connect to server' error and exactly:
WebSocket connection to 'wss://toto.prox.fr/api2/json/nodes/pve/qemu/100/vncwebsocket?port=5900&vncticket=PVEVNC%3A624BCBEC%3A%3AR%2Bk%2FcD5v5PNAKg1KzIgsi6Y6TO7dd44sL%2FeHRPHr8sr7PUDr9lczqe0HW5VdaYWWK9qw98264E0fij%2FwW%2BLjpv2tkemSQ8nPfhliVIjteF6ntaUWR5v7urbHiN6Im8ru3X8l6Fv8Iu2cGS5OvddTHzH3tVsZaIw1GegcZMkbM3i3C9Yokx1N21kFO4od7FnTVkuMEH9mY6e3dkcaFXgq7361cWxpOorvO3MDYKI8GD%2Fh%2FXgSdTZaHcrU5j605gMml%2Bon96%2B%2BAMj8yqWQajzWRYZgUPGBIpg5vUHZ%2Fg7NkBl%2B8u9lqopSYrAY76uiqGnl2zlX159w%3D%3D' failed.

I have a similar error when i want to access shell'pve from web api : undefined code : 1006

If i logged on the web Api with ip address, i can access to it.

Any idea ?

Regards
 
that is by design, the websocket connection has to have a valid pve auth cookie set in addition to the ticket in the url
 
And is there any option for how to bypass it?
Because, I'm using my own GUI on a different site as my Proxmo VE server, and there si absolutely zero chance to pass the cookie cross-site.
 
you'd have to have some kind of proxy that sets the cookie. either a self written one, or e.g. an nginx reverse proxy could maybe work (i don't know though, that's just an educated guess)