Out of nothing. Node-red not accessable via web browser

General
1

Out of nothing, I suddenly lost access to node-red via web browser.
Node-red are running on raspberry pi.
Tried to restart, and it seems that node-red are running, but no web access

Please help

pi@raspberrypi:~ $ node-red-start

Start Node-RED

Once Node-RED has started, point a browser at http://192.168.1.225: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.
31 Dec 02:09:21 - [info]
Welcome to Node-RED

31 Dec 02:09:21 - [info] Node-RED version: v4.1.2
31 Dec 02:09:21 - [info] Node.js version: v18.20.8
31 Dec 02:09:21 - [info] Linux 5.10.103-v7l+ arm LE
31 Dec 02:09:21 - [info] Loading palette nodes
31 Dec 02:09:27 - [info] node-red-contrib-shelly version: v11.6.8
31 Dec 02:09:27 - [info] Dashboard version 3.6.6 started at /ui
31 Dec 02:09:29 - [info] Settings file : /home/pi/.node-red/settings.js
31 Dec 02:09:29 - [info] Context store : 'default' [module=memory]
31 Dec 02:09:29 - [info] User directory : /home/pi/.node-red
31 Dec 02:09:29 - [warn] Projects disabled : editorTheme.projects.enabled=false
31 Dec 02:09:29 - [warn] Flows file name not set. Generating name using hostname.
31 Dec 02:09:29 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
31 Dec 02:09:29 - [info] Server now running at https://127.0.0.1:8443/
31 Dec 02:09:29 - [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.

31 Dec 02:09:32 - [info] Starting flows

2

Welcome to the forum @PowerZone21

Are you sure that the Pi's IP address is still 192.168.1.225?
What computer (and it's IP address) are you running the browser on?
Do you get an error in the browser or just a blank page?

Is this a Raspberry Pi 3B+?
You might want to make sure the OS is up to date, and also consider running the Raspberry Pi installation script again, specifying --node22 or --node24
Are you planning to migrate from the original dashboard, now deprecated?

3

This may not be related... but Windows 11 25H update that just was pushed out a week or so ago... aggravates a long term Windows 11 bug... which makes Windows 11 very chatty in reference to DNS queries.

So much so in my case that my PiHole (DNS query) rate limit was exceeded over and over. This triggers a symptom comparable that you note... When my Windows 11 system trips over this issue... the first sign of trouble is I get communication errors with NR. Flushing DNS cache helps but only reboot really helps for a while, the issue results again. There are many (upset) Windows 11 users that are talking about this issue.

The discussion is also on Microsoft Learn, community, PiHole community, etc. So far this long term bug is being ignored by the various parties, Microsoft, Intel (I happen to have Intel NICs), etc., with no real acknowledgement or fixes, just work-arounds. My Windows 11 system was fine for years until 25H hit, it was only then I found it the original bug was in 24H for at least a year.

In short, I have a Linux parallel system, and I am using it more and more... as a result of this bug. LOL... I happen to have a few Windows applications that cannot run under WINE, so I am not as yet able to completely abandon Windows.

Maybe time to get a Mac? LOL! Again?