Hi everyone
The last days I wanted to move my node red installation from a Raspian to a Home Assistant Server. After Installing the Node-Red Plugin in Home Assistand I imported my old flows from the previous installation. After some fideling with some nodes I was able to deploy the flows without errors while deploing.
But now when I call the /ui I allways get "Cannot GET /ui". Do you have any idea what this chould cause and how to fix it?
I allready deleted all nodes or even started with a new installation of node-red, but no luck. Surprising to me was that the flows were not deleted after reinstalling node-red on home-asistant. This means I was not able to get a very clean new installation after the first imports on the home-assistant-node-red.
Every Input or help is very welcome.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
Add-on: Node-RED
Flow-based programming for the Internet of Things
-----------------------------------------------------------
Add-on version: 6.2.0
You are running the latest version of this add-on.
System: HassOS 3.13 (armv7 / raspberrypi3)
Home Assistant Core: 0.109.1
Home Assistant Supervisor: 221
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] nginx.sh: executing...
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] node-red.sh: executing...
patching file nodes/ui_base.html
Hunk #1 succeeded at 1244 (offset 713 lines).
audited 317 packages in 9.591s
15 packages are looking for funding
run `npm fund` for details
found 1 high severity vulnerability
run `npm audit fix` to fix them, or `npm audit` for details
[cont-init.d] node-red.sh: exited 0.
[cont-init.d] user.sh: executing...
[cont-init.d] user.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[23:48:16] INFO: Starting Node-RED...
> addon-node-red@ start /opt
> node $NODE_OPTIONS node_modules/node-red/red.js "--settings" "/etc/node-red/config.js"
7 May 23:48:20 - [info]
Welcome to Node-RED
===================
7 May 23:48:20 - [info] Node-RED version: v1.0.5
7 May 23:48:20 - [info] Node.js version: v12.15.0
7 May 23:48:20 - [info] Linux 4.19.114-v7 arm LE
7 May 23:48:22 - [info] Loading palette nodes
7 May 23:48:28 - [info] Dashboard version 2.21.0 started at /endpoint/ui
7 May 23:48:32 - [info] Settings file : /etc/node-red/config.js
7 May 23:48:32 - [info] Context store : 'default' [module=memory]
7 May 23:48:32 - [info] User directory : /config/node-red/
7 May 23:48:32 - [warn] Projects disabled : editorTheme.projects.enabled=false
7 May 23:48:32 - [info] Flows file : /config/node-red/flows.json
7 May 23:48:32 - [info] Server now running at http://127.0.0.1:46836/
7 May 23:48:32 - [info] Starting flows
[23:48:32] INFO: Starting NGinx...
nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
7 May 23:48:33 - [info] Started flows
7 May 23:48:33 - [info] [mqtt-broker:700a60a5.6b77b] Connected to broker: mqtt://localhost:1883
7 May 23:48:33 - [info] [mqtt-broker:4b4129aa.4a0818] Connected to broker: mqtt://localhost:1883```
