Keeping Proxmox NoVNC Consoles Working Behind HAProxy Using Sticky Sessions

Placing a Proxmox VE cluster behind a round-robin HAProxy load balancer can break NoVNC WebSocket console sessions, because requests get routed to different nodes mid-session. The author explains that this invalidates authentication tickets and causes WebSocket handshakes to fail. Rather than using a single backend or abandoning round-robin, the author chose to enable session persistence with HAProxy cookie-based sticky sessions. The article provides a full backend configuration that pins each browser session to one Proxmox node, including health checks and forwarded headers. According to the author, the console stays accessible even when an individual node goes offline for maintenance.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in