[BUG] Combo Studio frontend ignores proxy variables and forces hardcoded WebSocket port 20132 (/live-ws) #11331

OmniRoute Version

v3.8.49 (latest)

Installation Method

Docker / Docker Compose

Operating System

Linux

OS Version

Alma Linux 10

Node.js Version

No response

Provider(s) Involved

No response

Model(s) Involved

No response

Client Tool

Web Interface

Description

When deploying OmniRoute in a rootless container (Podman/Docker) behind a reverse proxy (Traefik) on port 443, the Combo Studio dashboard fails to connect to the live tracking socket. The UI constantly states: Live disabled — WebSocket disconnected. Showing last known state.

Inspecting the network traffic reveals that the frontend UI ignores container-side environment configuration variables (LIVE_WS_PORT) and blindly attempts to establish a client-side connection directly to wss://omniroute.domain.tld:20132/live-ws.

Steps to Reproduce

1. Deploy OmniRoute inside a Podman container.
2. Proxy the container via Traefik routing standard traffic to the primary web interface port (PORT=20128).
3. Set environment parameters LIVE_WS_HOST=0.0.0.0 and attempt to override the socket port.
4. Access the dashboard externally via HTTPS/443 and navigate to Combo Studio.
5. Inspect the Network Tab (WS filter).

Expected Behavior

The frontend should recognize when it is being served via a reverse proxy/different port context and build its WebSocket handshake relative to the origin host/port (e.g., using a standard path prefix like /live-ws over the established web port), or respect a client-facing environment configuration variable.

Actual Behavior

The browser attempts a connection directly to external port 20132, completely bypassing the proxy topology and failing.

Test Impact

Unsure

Error Logs / Output

Screenshots

No response

Additional Context

It seems like src/hooks/useLiveDashboard.ts function getDefaultWsUrl() hardcodes literal WebSocket port 20132 on every browser-side path, ignoring the server's actual LIVE_WS_PORT config.

Validation Plan

No response