Repository navigation
bug(frontend): WebSocket URL has two conflicting sources of truth — build-time VITE_* vs runtime /api/frontend-config #6232
Description
Summary
Two sources of truth for the WebSocket URL currently disagree, causing LiveEventService to dial the wrong endpoint depending on how it reads config.
Conflict
| Source | Value |
|---|---|
Build-time SSOT (VITE_HTTP_PROTOCOL + VITE_AI_STACK_HOST etc. baked into ssot-config) |
wss://172.16.168.20/live |
Runtime GET /api/frontend-config |
ws://127.0.0.1:8001/ws |
Required fix
Pick one source of truth — recommend runtime /api/frontend-config so deployments don't require a frontend rebuild to change the URL:
- Update
LiveEventServiceto read the WS URL from/api/frontend-config(fetch once on init, before dialling). - Update
/api/frontend-configto return the canonical path chosen in bug(backend): WebSocket endpoint not registered — LiveEventService reconnects every ~7 s on all pages #6229 (e.g.wss://<host>/api/ws). - Drop or mark-deprecated the
VITE_*WebSocket vars to prevent future confusion.
Dependencies
- bug(backend): WebSocket endpoint not registered — LiveEventService reconnects every ~7 s on all pages #6229 (backend WebSocket endpoint) must define the canonical path first.
- bug(nginx): missing WebSocket upgrade location block — WS connections fall through to SPA index.html #6230 (nginx upgrade block) must also use the same path.
Priority
P1 — even after #6229 and #6230 are fixed, LiveEventService may still dial the wrong URL if this is not reconciled.
Activity
fix(frontend/backend): unify WebSocket URL to /api/ws in ssot-config …
mrveiss commentedon Apr 27, 2026
✅ Closed — implementation merged to Dev_new_gui.
Merge commit: d3cb514
Acceptance criteria met:
ssot-config.tswebsocketUrlcorrected from/ws→/api/wsssot_config.pywebsocket_urlcorrected to/api/wswithwss://TLS support/api/frontend-confignow exposesservices.websocket.urlfor runtime validationWiring verified:
_build_frontend_services_configinsystem.py:124is called byGET /api/frontend-configDiscovery issues filed: none
fix(frontend/backend): correct WebSocket URL path and HTTPS port (#6232…
mrveiss commentedon Apr 27, 2026
✅ Closed — implementation merged to Dev_new_gui.
Merge commits:
d3cb514c0fix(frontend/backend): unify WebSocket URL to /api/ws in ssot-config and frontend-config endpoint (fix(frontend/backend): unify WebSocket URL to /api/ws in ssot-config and frontend-config endpoint (#6232) #6271) — fixed path/ws→/api/wsfor HTTP casee2d9fca74fix(frontend/backend): correct WebSocket URL path and HTTPS port (fix(frontend/backend): correct WebSocket URL path and HTTPS port (#6232) #6283) — fixed HTTPS production case (removed port, routing through nginx)Acceptance criteria met:
ssot-config.tswebsocketUrlgetter: HTTPS →wss://host/api/ws(no port, through nginx TLS); HTTP dev →ws://host:8001/api/wsnetwork_constants.pyget_websocket_url(): returns/api/wspathfrontend_config.pyfallback: WebSocket URL uses/api/wspathLiveEventServiceconnects to${websocketUrl}/live=/api/ws/livewhich matches backend route registered at/api/ws/liveWiring verified: No new public symbols introduced
Discovery issues filed: none
mrveiss commentedon Apr 27, 2026
✅ Fixed in Dev_new_gui.
Commit: e2d9fca fix(frontend/backend): correct WebSocket URL path and HTTPS port (#6232) (#6283)
Verified: fix present in
origin/Dev_new_guiviagit log --grep='#6232'.fix(frontend): update WEBSOCKET_LOCAL to /api/ws path — missed by #6232…