Raspberry pi2: nodered is accessible only via ip

Hi !

first time here for me, and first day with node red.

I installed nodered on a fresh and clean OS on a pi2 model 2

I can login via ssh using "raspberrypi.local" as hostname from my windows machine, without having to add entry into /etc/hosts

I can see node-red using device's IP (hostname -I) , for example I can access using

But i cannot access node-red using device's hostname. I cannot access using


From an old 2013 post (1) is still relevant today and will definitely work)

  1. (Always works) On the machine that you are ssh'ing from (say, your "laptop" or whatever), put an entry in the /etc/hosts files (for Unix/Linux/Mac, it is /etc/hosts. On Windows, it is C:\windows\system32\drivers\etc\hosts), associating the IP address with a name. Then you can use that name in future. This always works, but the annoyance is that you have to do it on each machine that you want to be able to ssh from.

  2. (Works sometimes, sometimes not - you know, phase of the moon, whether or not the hour is odd or even, probably other factors involved) Install "avahi-daemon" on the Pi. When this works, it is great. It makes the hostname of the Pi visible on your LAN. Then you can use that hostname in your "ssh" command.

Newer info here: linux - Why can't I reach my raspberry pi with the hostname I set for it? - Super User

thanks for reply

the hostname is already visible on net. I already can login via ssh using hostname
only the webserver of nodered gui is not reachable using hostname

I actually cannot save hostname as entry in /etc/hosts because raspberry it's installed under dhcp.

.local working is just up to how the gremlins are feeling on the day in question

I've just put up with this for past years and just switch to IP when it doesn't work

Currently getting away with using name (minus the .local) this week (from my Win11 machine)


1 Like

Your reply is making me happy . thanks

Today i can confirm i can access without .local.

I'll recheck tomorrow.
Thanks to all

And for the day after tomorrow, see if your router or other local DNS supports "hairpin NAT". This lets you define domain names that point to local IP's when running on the local network even though they point to Internet addresses when working elsewhere.

The great advantage being that you can use a publicly validated TLS certificate for both external and internal use. And, of course, you can use the same URL inside and out (if you expose your Node-RED endpoints to the Internet that is - fully secured of course).

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.