[SOLVED] Working NoVNC with reverse proxy on 5.1

[linkedcorp]

View attachment 74610

i've enabled this in my nginx proxy manager and now i can connect to console when connected externaly thru proxmox

Thks, that was my case, i apply this solution and like a magic the console noVNC works.!!! i dont touch any config file... again thks.

 

[tconnors]

I got this working using a single pve, but how do you use the balance module to balance across multiple PVEs?

So far I've got the kitchen sink loaded but struggling to understand what to use for the wss rewrite target. See example below with the commented line being the wss rewrite.

Perhaps a year and a half too late for you (meh, I only added this to my TODO list a couple of years ago), but I just managed to get console passthrough on my load balanced cluster:

https://github.com/spacelama/ansibl...pache2.webserver.ext/sites-enabled/2-pve.conf

The requirements was that it had to use apache, because it had to hook into my certbot installation that's already enabled on my external apache webserver. http(s)?://pve.$domain is publicly accessible, for the purposes of certbot to renew the certs. But it and the raw http(s)?://pve vhosts then immediately results in the redirection, not proxying, to https://pve.$domain:8006, which isn't publicly accessible. That then load balances, with upgrade=websocket (didn't bother restricting to any paths - the pve.$domain endpoint is just for proxmox) to the actual proxmox nodes.