node-RED can not be opened anymore

I changed it to flow_new.json

but nothing happend

Well the good news is that its not something in your flow so you can move it back.
and Node-red is running you just can't access it.

This means it has to be something in your install.

Have you installed any "dashboards" recently - any other nodes that say they have dashboard functionality. If so I would start by removing them ( and removing the two that Node-RED is complaining about as well)

No the only dashboard i have installed is the node-red-dashboard.

after I removed the two they are still in there!

but in the node_modules file both are not existing.

but you aren't in the correct directory to run that command.

cd .node-red

ok I run the command now in the correct directrory, now this appears

Those are just warnings (about the nodes you removed). They should not appear again.
By the way it is better, if possible, to copy/paste here rather than insert images. You can copy/paste from the terminal using Ctrl-Shift-C. When pasting logs use the same technique for making sure they show ok as is used for code/flows.

ok the next log i will share so.

After a new reboot of node-red the warning don´t appear again.

pi@H0028631:~ $ node-red-stop

Stop Node-RED
 
Use   node-red-start   to start Node-RED again
 
pi@H0028631:~ $ node-red-start
#
Start Node-RED
 
Once Node-RED has started, point a browser at http://10.21.42.235:1880
On Pi Node-RED works better with the Firefox or Chrome browser
 
Use   node-red-stop                          to stop Node-RED
Use   node-red-start                         to start Node-RED again
Use   node-red-log                           to view the recent log output
Use   sudo systemctl enable nodered.service  to autostart Node-RED at every boot
Use   sudo systemctl disable nodered.service to disable autostart on boot
 
To find more nodes and example flows - go to http://flows.nodered.org
 
Starting as a systemd service.
Started Node-RED graphical event wiring tool.
9 Jan 10:17:18 - [info]
Welcome to Node-RED
===================
9 Jan 10:17:18 - [info] Node-RED version: v0.19.5
9 Jan 10:17:18 - [info] Node.js  version: v8.12.0
9 Jan 10:17:18 - [info] Linux 4.14.70-v7+ arm LE
9 Jan 10:17:19 - [info] Loading palette nodes
9 Jan 10:17:22 - [info] Dashboard version 2.12.2 started at /ui
9 Jan 10:17:23 - [info] Settings file  : /home/pi/.node-red/settings.js
9 Jan 10:17:23 - [info] HTTP Static    : /home/pi/Pictures
9 Jan 10:17:23 - [info] Context store  : 'default' [module=memory]
9 Jan 10:17:23 - [info] User directory : /home/pi/.node-red
9 Jan 10:17:23 - [warn] Projects disabled : editorTheme.projects.enabled=false
9 Jan 10:17:23 - [info] Flows file     : /home/pi/.node-red/flow_new.json
9 Jan 10:17:23 - [info] Server now running at http://127.0.0.1:1880/
9 Jan 10:17:23 - [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.
---------------------------------------------------------------------
9 Jan 10:17:23 - [info] Starting flows
9 Jan 10:17:23 - [error] [users_config:86a81de6.9ee2d] Node users config is missing
Secret =  Hans
2019-01-09 09:17:24: Connecting to modbustcp slave at 192.168.1.5:502 unit_id: 1
2019-01-09 09:17:24: Connecting to modbustcp slave at 192.168.1.5:502 unit_id: 1
2019-01-09 09:17:24: Connecting to modbustcp slave at 192.168.1.5:502 unit_id: 1
2019-01-09 09:17:24: Connecting to modbustcp slave at 192.168.1.5:502 unit_id: 1
9 Jan 10:17:24 - [info] Started flows

but what is with the [warn] without any comment?

That warn is about the following credentials message.
I see you have an error there still

9 Jan 10:17:23 - [error] [users_config:86a81de6.9ee2d] Node users config is missing
Secret =  Hans

Do you know what that is about? If not then you can search for the node id (86a81de6.9ee2d) using the Search feature under the hamburger menu to find that node to see what is wrong.

what is the hamburger menu?

this would have to be because i used the node-red-contrib-user node. Actually, I also uninstalled this

The three lines in the top right
image

Do you mean you get this message after uninstalling? In which case there is likely an unused config node left. When you click Deploy you should see a message saying Unused Config Nodes. Click that and it will take you to it so you can delete it. Alternatively you can get to the config nodes from the hamburger menu and will see unused ones. To delete it open it and click Delete

I can´t reach the node-RED editor. Node-RED is running but I acces to the editor or dashboard!

have no acces to Editor or Dashboard I mean

Paste a screenshot of what you see in the browser when you try to get to it, including the address bar of the browser.
Also tell us whether the browser is running on the same machine as node red.
If it is on a different machine then on the node-red machine, in a terminal, run

ifconfig

and paste the result here

the browser don´t run on the same machine as node-red

the same result is when i try to access the editor on the raspberry pi with 127.0.0.1:1880

Looking back at what you said earlier, you said that you had renamed the flow file to flow_new and restarted node-red, but the log you posted shows it using that flow when it should have made a new empty one. Can you rename it again and restart node red. Don't do anything else. Then you should see it starting with a new empty flow.

ok now i can reach the editor again :smiley:

Was my flow the reason why it stopped working? or can I import my old flow again

1 Like

Yes, something in there was causing a hangup and preventing it from fully starting. There should be a backup flow called
.flows_H00something.json.backup where you can see the name in the first log you posted, I can't easily read the screenshot. Note the dot on the front of the filename. If that is there then it should be the flow from before you made the last change. First make a copy of it under a different name so you can get it back if you want it, then rename it to whatever your current flow file name is and try that.

ok thanks for support.

I imported the old flow and Node-RED works fine :+1:

The moral is to keep regular backups of your flow.

there you are right, I do a weekly backup, maybe I'll do some more now