Cannot start any addons

Yesterday I installed a fresh copy of HA OS on a VM running on virtual box. I then restored from a backup of a previous installation I’d had up and running for a few weeks. In the new installation, I have not been able to get any add-on to start. Addons I had been using were: node-red, Eufy Security Addon, RTSP Simple Server Add-on, and Terminal & SSH.

Now, I cannot get any of these to start. There are no errors of any kind anywhere in logs. When I click start, the button spins briefly, and then…nothing. I have restarted HA, cleared my cache, and uninstalled and reinstalled the addons.

Below is the log from Node-red as an example:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/00-banner.sh
-----------------------------------------------------------
 Add-on: Node-RED
 Flow-based programming for the Internet of Things
-----------------------------------------------------------
 Add-on version: 13.3.1
 You are running the latest version of this add-on.
 System: Home Assistant OS 8.4  (amd64 / qemux86-64)
 Home Assistant Core: 2022.8.3
 Home Assistant Supervisor: 2022.08.3
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
cont-init: info: running /etc/cont-init.d/customizations.sh
cont-init: info: /etc/cont-init.d/customizations.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
cont-init: info: running /etc/cont-init.d/node-red.sh
patching file nodes/ui_base.html
Hunk #1 succeeded at 1164 (offset 633 lines).
up to date, audited 1 package in 364ms
found 0 vulnerabilities
cont-init: info: /etc/cont-init.d/node-red.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun nginx (no readiness notification)
services-up: info: copying legacy longrun nodered (no readiness notification)
s6-rc: info: service legacy-services successfully started
[19:48:25] INFO: Starting Node-RED...
> start
> node $NODE_OPTIONS node_modules/node-red/red.js "--settings" "/etc/node-red/config.js"
11 Aug 19:48:28 - [info] 
Welcome to Node-RED
===================
11 Aug 19:48:28 - [info] Node-RED version: v3.0.2
11 Aug 19:48:28 - [info] Node.js  version: v16.16.0
11 Aug 19:48:28 - [info] Linux 5.15.55 x64 LE
11 Aug 19:48:29 - [info] Loading palette nodes
11 Aug 19:48:32 - [info] Dashboard version 3.1.7 started at /endpoint/ui
11 Aug 19:48:33 - [info] Settings file  : /etc/node-red/config.js
11 Aug 19:48:33 - [info] Context store  : 'default' [module=memory]
11 Aug 19:48:33 - [info] User directory : /config/node-red/
11 Aug 19:48:33 - [warn] Projects disabled : editorTheme.projects.enabled=false
11 Aug 19:48:33 - [info] Flows file     : /config/node-red/flows.json
11 Aug 19:48:33 - [warn] Encrypted credentials not found
11 Aug 19:48:33 - [info] Server now running at http://127.0.0.1:46836/
11 Aug 19:48:33 - [info] Starting flows
11 Aug 19:48:33 - [info] Started flows
[19:48:33] INFO: Starting NGinx...
11 Aug 19:48:38 - [info] [server:Home Assistant] Connecting to http://supervisor/core
11 Aug 19:48:38 - [info] [server:Home Assistant] Connected to http://supervisor/core
11 Aug 20:01:54 - [info] [server:Home Assistant] Connection closed to http://supervisor/core
11 Aug 20:01:59 - [info] [server:Home Assistant] Connecting to http://supervisor/core
11 Aug 20:02:04 - [info] [server:Home Assistant] Connecting to http://supervisor/core
11 Aug 20:02:09 - [info] [server:Home Assistant] Connecting to http://supervisor/core
11 Aug 20:02:14 - [info] [server:Home Assistant] Connecting to http://supervisor/core
11 Aug 20:02:19 - [info] [server:Home Assistant] Connecting to http://supervisor/core
11 Aug 20:02:24 - [info] [server:Home Assistant] Connecting to http://supervisor/core
11 Aug 20:02:25 - [info] [server:Home Assistant] Connected to http://supervisor/core

Even though the last line of the log says connected, Node-red is not started, and I cannot load the interface.

So I’ll put an update here in case anyone finds this useful in future. I’m not entirely sure that this was the fix, but I shut down the virtual machine, generated a new MAC address for it, and restarted, and everything magically worked again. So seems like it may have reused a MAC address from a previous install, or something. For whatever reason, the MAC address that virtualbox had assigned was causing problems. I’m quite sure that I don’t fully understand what actually happened here, but it’s back up now.

3 Likes

I’m having this same problem after migrating my HA from a windows hypervisor VM to a VMware one. How did you reassign a Mac address? Also, how did you discover this to be the problem?

did the trick for me thanks for the follow up