"Error: Invalid server config" when upgrading to 13.5.0
See original GitHub issueProblem/Motivation
Left my house this morning with my all of my automations working. Came home to none of my automations working. Each node in Node-RED having the state “error” and log is full of the following:
27 Oct 21:10:00 - [error] [api-current-state:8d5d7add97166c02] Error: Invalid server config
27 Oct 21:10:00 - [error] [api-current-state:ba7c6dc22430e3ef] Error: Invalid server config
27 Oct 21:10:00 - [error] [server-state-changed:3e1a436a4aa3bc4c] Error: Server config node not found
27 Oct 21:10:00 - [error] [api-call-service:60af4994936ecc08] Error: Server config node not found
27 Oct 21:10:00 - [error] [api-call-service:7feeba8fdb016e27] Error: Server config node not found
According to my logs, the Node-Red plugin auto-updated from 13.4.0 to 13.5.0. Restored the add-on from a backup taken before the upgrade and the errors are gone and automations are working. Upgrade to 13.5.0 and it the it fails the same way. I’ve repeated the process of restoring and upgrading 3 times, and the problem comes back every time.
Expected behavior
Automations run.
Actual behavior
No automations run.
Steps to reproduce
Update to 13.5.0
Proposed changes
No idea.
Issue Analytics
- State:
- Created a year ago
- Comments:9
Top Results From Across the Web
Node-Red 13.5.0 server config errors
Recently upgraded to 13.5.0. After upgrade ALL my Node-Red automations failed tp work. Was getting “no server found” and “invalid server ...
Read more >13.5.0 Enterprise Manager Cloud Control Base Platform ...
Bug Component Sub Component Release
33927269 MONITORING RUNBOOKS 13.5.0.0.220331EM‑OMS‑BP
33883923 OMS 13.5.0.0.220331EM‑OMS‑BP
33890397 MONITORING RUNBOOKS 13.5.0.0.220331EM‑OMS‑BP
Read more >OEM silent upgrade from 13.4 to 13.5 failed with ...
OEM silent upgrade from 13.4 to 13.5 failed with WLS_ADMIN_SERVER_PASSWORD not set error. I was working on upgrading my OEM 13.4 installation to ......
Read more >Issues · hassio-addons/addon-node-red - GitHub
Home Assistant - Unable to install new palettes or update installed ones. ... "Error: Invalid server config" when upgrading to 13.5.0.
Read more >Upgrade Enterprise Manager Cloud Control to 13.5
So – if you are you using BI Publisher in your current OEM setup, you should export the report prior to the upgrade;...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I ran into this same issue when upgrading from 13.4.0 to 13.5.0 - and downgraded to get our automations running. After seeing the above post from @Nealtron I decided to look into the Node-Red settings to see if I also had something strange in the server node name field.
I had never touched the server node settings inside Node-Red so the values and structure most likely originated from some very old version of this addon. My server name is also very default “Home Assistant” so I did not change that, but I noticed that there was an unchecked checkbox “Using the Home Assistant Add-on” (it was working just fine without it - and might been doing so for who knows how long as I had never even looked at these).
I checked the box and everything continued to work in 13.4.0. I then upgraded to 13.5.0 and now it also works fine.
Maybe the settings needed just some change to get them saved in a more compatible format? Or maybe this “Using the Home Assistant Add-on” was previously not needed but is now mandatory.
@jjlink Open the Node-RED webui. Click on the menu button the top right, and click on “configuration nodes”. Make sure you are looking under “On all flows” and look for “server” nodes. More than likely, you’ll only have one. Double click it to modify.