Hello everyone,
I'm experiencing an issue with the Proxmox web console when accessing my server remotely through port forwarding. The Proxmox web interface is accessed through my public IP, but the browser's WebSocket connection fails in every few minutes.
I am trying to determine why the WebSocket connection is being refused even though I am accessing the Proxmox web interface through the external port.
Thank you!
I'm experiencing an issue with the Proxmox web console when accessing my server remotely through port forwarding. The Proxmox web interface is accessed through my public IP, but the browser's WebSocket connection fails in every few minutes.
My Network Configuration
- Proxmox internal IP: 192.168.1.11
- Proxmox web interface port: 8006
- External port: 8888
- Port forwarding method: Router NAT / port forwarding
- Access URL: https://<PUBLIC-IP>:8888
The Problem
When I open a shell through the Proxmox web interface, after using for few minutes or even seconds, the browser reports the following errors:- Connection closed: Code 1006.
- In the browser's Developer Tools → Network → WS tab, the connection fails with:
I am trying to determine why the WebSocket connection is being refused even though I am accessing the Proxmox web interface through the external port.
What I Have Checked
- The router is configured to forward external port 8888 to internal IP 192.168.1.11 on port 8006.
- I am accessing Proxmox directly through HTTPS using the public IP and external port.
- I am not using Nginx, HAProxy, Cloudflare Tunnel, or another reverse proxy.
Questions
- Does Proxmox require any additional configuration to support WebSocket connections when accessed through router NAT port forwarding?
- Could Proxmox be generating a WebSocket URL that uses internal port 8006 instead of the externally forwarded port 8888?
- Are there any specific pveproxy, firewall, or network settings I should check?
- What is the recommended way to diagnose ERR_CONNECTION_REFUSED for the console WebSocket connection?
Thank you!