Broke Node-red. All options are blank

I'm not sure what I did. Node-Red 0.20.7 has been running perfectly. Actually, everything is still working, but I'm missing all the options inside the Nodes. Like drop downs, etc are all blank. Has anyone seen this?

I uploaded an example. I'm not seeing any errors in Journalctl.


When you restart node-red it posts startup messages can you copy and paste those startup message here

Thanks Ukmoose,

22 Aug 11:28:10 - [info] Node-RED version: v0.20.7
22 Aug 11:28:10 - [info] Node.js version: v11.15.0
22 Aug 11:28:10 - [info] Linux 4.19.62-1-MANJARO x64 LE
22 Aug 11:28:11 - [info] Loading palette nodes
22 Aug 11:28:15 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
22 Aug 11:28:15 - [warn] rpi-gpio : Cannot find Pi RPi.GPIO python library
22 Aug 11:28:16 - [info] Settings file : /root/.node-red/settings.js
22 Aug 11:28:16 - [info] Context store : 'default' [module=memory]
22 Aug 11:28:16 - [info] User directory : /root/.node-red
22 Aug 11:28:16 - [warn] Projects disabled : editorTheme.projects.enabled=false
22 Aug 11:28:16 - [info] Flows file : /root/.node-red/flows_DeepLearning.json
22 Aug 11:28:16 - [info] Creating new flow file
22 Aug 11:28:16 - [warn]

Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.

22 Aug 11:28:17 - [info] Starting flows
22 Aug 11:28:17 - [info] Started flows
22 Aug 11:28:17 - [info] Server now running at

There’s nothing directly there that could cause it.

But you are running nodejs v11 which isn’t recommended. The recommended versions are LTS currently v10

That would probably be causing problems with the serial nodes.

You are also running as root, which shouldn’t be necessary.

In fact, running Node-RED as root is a bad idea in general. If you have a specific reason why you need to run it as root, try to figure out a workaround using the sudoers file or permissions elsewhere to get a lower user run it. But really, there are no valid reasons to run it as root. Especially not because with the exec node it runs all commands as root, and it comes with a web interface to edit those. There are a few topics on this already mentioning this...

Thanks all. I'll probably blast this install and redo it.