Dashboard WebSocket 'Connection lost' on Add-on v20.0.0 #2118
Description
Hello
My Setup:
Add-on Version: v20.0.0
===================
3 Oct 11:39:44 - [info] Node-RED version: v4.0.9
3 Oct 11:39:44 - [info] Node.js version: v22.16.0
3 Oct 11:39:44 - [info] Linux 6.12.43-haos x64 LE
3 Oct 11:39:44 - [info] Loading palette nodes
3 Oct 11:39:44 - [info] Node-RED Contrib Theme Collection version: v4.0.11
3 Oct 11:39:45 - [info] Dashboard version 3.6.5 started at /endpoint/ui
3 Oct 11:39:46 - [info] node-red-contrib-home-assistant-websocket v0.77.1 nodes initialized
3 Oct 11:39:46 - [info] Settings file : /etc/node-red/config.js
3 Oct 11:39:46 - [info] Context store : 'default' [module=memory]
3 Oct 11:39:46 - [info] User directory : /config/
3 Oct 11:39:46 - [warn] Projects disabled : editorTheme.projects.enabled=false
3 Oct 11:39:46 - [info] Flows file : /config/flows.json
3 Oct 11:39:46 - [info] Server now running at http://127.0.0.1:46836/
3 Oct 11:39:46 - [info] Starting flows
[11:39:46] INFO: Starting NGinx...
3 Oct 11:39:46 - [info] Started flows
3 Oct 11:39:46 - [info] [server:Home Assistant] Connecting to http://homeassistant.local:8123
3 Oct 11:39:46 - [info] [mqtt-broker:Mosquitto Broker] Connected to broker: mqtt://core-mosquitto:1883
3 Oct 11:39:46 - [info] [server:Home Assistant] Connected to http://homeassistant.local:8123
Problem:
The Node-RED Dashboard UI loads, but immediately shows a "✘ Connection lost" error when i submit a prompt - preventing any interaction.
Troubleshooting Steps Taken:
Confirmed node-red-dashboard is installed via npm_packages.
Logs confirm the dashboard starts successfully at /endpoint/ui.
Accessing via direct IP (http://:1880/endpoint/ui) loads the page but results in the "Connection lost" error.
Accessing via Home Assistant Ingress (.../ingress/endpoint/ui) incorrectly redirects to the editor, not the dashboard.
Tried multiple settings.js configurations, including setting httpNodeRoot: '/', with no effect on the error.
Confirmed the dashboard_ingress: true setting is not valid for this version.
This appears to be a bug in how network connections and paths are handled in this version of the add-on.