Nope. The NodeRd Pi is connected via wire (only) to one subnet. The client Pi is connected via WiFi (only) to the other subnet. I have also tested with a client wired to the subnet used by the WiFi access point and it has the same problem.
Hi, Collin -
I installed NR using the following:
bash <(curl -sL https://raw.githubusercontent.com/node-red/linux- *installers/master/deb/update-nodejs-and-nodered
As requested, I started NR in a terminal session and the startup text is below. Is there a separate log that I should post?
Thanks!
=======================================================================
pi@raspberrypi: Node-RED console
Start Node-RED
Once Node-RED has started, point a browser at 192.168.80.80: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 flows.nodered.org
Starting as a systemd service.
26 Aug 08:03:55 - [info]
Welcome to Node-RED
===================
26 Aug 08:03:55 - [info] Node-RED version: v2.0.5
26 Aug 08:03:55 - [info] Node.js version: v14.17.5
26 Aug 08:03:55 - [info] Linux 5.10.50-v7l+ arm LE
26 Aug 08:03:56 - [info] Loading palette nodes
26 Aug 08:03:57 - [info] Dashboard version 2.30.0 started at /ui
26 Aug 08:03:57 - [info] Settings file : /home/pi/.node-red/settings.js
26 Aug 08:03:57 - [info] Context store : 'default' [module=memory]
26 Aug 08:03:57 - [info] User directory : /home/pi/.node-red
26 Aug 08:03:57 - [warn] Projects disabled : editorTheme.projects.enabled=false
26 Aug 08:03:57 - [info] Flows file : /home/pi/.node-red/flows.json
26 Aug 08:03:57 - [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.
---------------------------------------------------------------------
26 Aug 08:03:58 - [info] Server now running at 127.0.0.1:1880/
26 Aug 08:03:58 - [info] Starting flows
26 Aug 08:03:58 - [info] Started flows
Originally you said the pi is running on 192.168.100.100 but this says it is running on 192.168.80.80
what changed?
I had the wrong info in my original post. The Pi is in fact running at 192.168.80.80., not 192.168.100.100.
Can you setup a ping node on node-red and have it ping the other side of the firewall so we can see if this is a one or two way error ?
Craig
Do you have a linux box on the other (non node red subnet) - can you try and telnet from the commandline on it to port 1880 on the NR box and see if anything is reported back
Craig
Hi, Craig;
I can successfully ping in both directions between the NR box and a Pi on the other subnet.
Telnet times out. However, I have another box running NGINX on the same subnet as the NR box and I have configured it to listen on port 1880. I can browse to it from the other subnet without a problem and telnet connects too. So it looks like the problem is on the NR box.
Do you know if NR creates a connection log somewhere? I have been unsuccessful looking for one. The command node-red-log doesnāt appear to show connections. Iāve also looked at /var/log/syslog and it shows NR starting (and, later stopping) but it doesnāt show any connection info.
Iām baffled by thisā¦
I do not believe it creates any sort of special connection log.
A couple of things - on the NR box - can you run
netstat | grep 1880 and see what it says
Craig
Can you install node red on another box on the network NR is on and see whether it exhibits the problem?
Result of "netstat | grep 1880":
unix 2 [ ] DGRAM 18804
unix 2 [ ] DGRAM 18801
I did a clean install of the operating system and NR on a PI and that configuration exhibits the same problem. Previously I did a clean install of the operating system and then installed the NGINX web server, configured it for port 1880, and was able to access it from both subnets. These installations were on separate SD cards so I could switch back and forth and confirm that the problem applied only to the NR installation. Both configurations used the same IP address.
Sorry, I meant s completely different install on an unrelated system, a Windows pc for example.
I think maybe that should be
sudo netstat -tulpn|grep 1880
SOLVED!
My NodeRed server runs on a Pi that is connected to my wired LAN. Normally , traffic from the second subnet is routed to NodeRed through that connection. However, by default Pi's enable WiFi if available and my NodeRed server made a second connection to my WiFi. As a result, there were two paths to the NodeRed server from the second subnet, one through the router to the wired connection and the other direct to the WiFi port. Some programs, like "ping" work correctly in that environment but NodeRed does not. I turned WiFi off on the NodeRed server Pi and that fixed the problem.
Thanks to everyone who provided help with this issue!
Perhaps you should mark @craigcurtin's post, where he suggested that, as the solution.
As suggested, I have marked @craigcurtin's post as the solution. I had forgotten that he raised this exact issue. At the time of his post I checked the configuration on the NodeRed Pi and the WiFi settings were blank -- but I now realize that didn't mean WiFi was disabled, just that it was getting its settings via DHCP. I'm embarassed to have made such a rookie mistake!
1 Like
Glad we got you over the line and resolved this one
Dont forget to screw those firewall settings back down now - now that is a rookie mistake to make to forget they are open in the euphoria of a working solution !
Craig
Hi, Craig;
Thanks for the reminder. I did remove the āallow all-allā test rule this morning, but Iāll check again to make sure I didnāt overlook anything else on the firewall.
--John
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
