Can't login in to Node-RED

Hello all,

I can’t login to Node-RED.

Have installed the addon with home assistant on a Raspberry Pi 3 and followed the configuration steps as described on the addon-node-red github page.

There are no problems in the log when running node red and the web UI login screen is reachable.

When filling in the user name and password and hit the login button. The login screen keeps refreshing and the username and password field are blank again, there were no login errors.

It’s not possible to get pass the login screen.

I tried it with Firefox, Chrome and IE, but with no success.

Has anyone encountered the same problem and found a solution?

1 Like

Just to let you know - I have the same situation and trying to find a solution.
Unfortunately didn’t find it yet.

I just installed it and made all the settings. According to log - everything is working fine.
The situation is exactly as you described.

Same for me :frowning:

I have used this sequence and it worked for me

$ sudo apt -y update
$ sudo apt -y upgrade
$ sudo raspi-config
– config hostname
– config timezone
– enable ssh

$ sudo shutdown -r now
login via ssh

Now install npm & n

$ sudo apt -y install npm
$ sudo npm install -g n
$ sudo n stable

Now nstall node-red

$ bash <(curl -sL
$ cd ~/.node-red
$ npm rebuild

Now setup Autostart on boot

$ sudo wget -O /lib/systemd/system/nodered.service
$ sudo systemctl daemon-reload
$ sudo systemctl enable nodered.service
$ sudo shutdown -r now

>avoid external calls to ha

Now install samba

$ sudo apt install samba samba-common-bin winbind
$ sudo mkdir -m 1777 /share
$ sudo nano /etc/samba/smb.conf
workgroup = WORKGROUP

Comment = Pi shared folder
Path = /home/pi
browseable = yes
writeable = Yes
only guest = no
create mask = 0777
directory mask = 0777
Public = yes
Guest ok = yes

Comment = Pi shared folder
Path = /home/pi/.node-red
Browseable = yes
Writeable = Yes
only guest = no
create mask = 0777
directory mask = 0777
Public = yes
Guest ok = yes

$ sudo /etc/init.d/samba restart

Now install webmin (light overhead but useful)

$ sudo apt-get install perl libnet-ssleay-perl openssl libauthen-pam-perl libpam-runtime libio-pty-perl apt-show-versions python
$ wget
$ sudo dpkg --install webmin_1.890_all.deb

But you are not running HASSIO and the add-on, like the others have stated…your setup is 100% different than theirs.

yeah, thats right … missed that part.

On the other hand … NR is working absolutely smooth for me (had the Add-on version before)

Me too. I use docker containers and don’t mess with hassio. I see a lot of issues around here regarding hassio.

Thank you for replying,

Found the problem…

Somehow my virus-scanner (Bitdefender) was blocking traffic from http://hassio.local:1880 without informing me.

I added a rule to allow traffic from http://hassio.local:1880 and problem solved.


Thanks Owi! Perfect!
I’m also using BitDefender and noticed after your comment that it blocked traffic 86 times without any info! (sic!)

By the way I see that there are rumors regarding Hassio, but this time you cannot say hassio fault.
I must say the Home Assistant project is great and hope it will keep on growing!

No antivirus software and no adblock add-on but facing same situation with @Owi . Is there a way to install any packet manager (like apt, yum) to hass to install node-red manually? Or any solution suggestion?

Edit:I couldn’t find a way to add an exception on firefox but, both Chrome and Opera can login to node red.

I have Node-Red installed on a dedicated RPi and have no access issues with HA or other network components

No. That’s not how docker works.

This issue drove me crazy, kept typing my user and pass from my Node RED config. For some reason this works the first time you load node red. Once you reboot, you need to login to Node RED with your user and pass for your install. Giggity! Good luck, hope that helps. Drove me insane for an hour.

1 Like

This actually got me past the login screen/box, but the result was a blank page with this text: “Cannot GET /ui”…
Now on to research this error…

Found the answer here:
If I had read the documentation when installing I could have caught it then…

This worked for me too! @chenzomo if I hadn’t read this I’d never have guessed to try my hass credentials. Well done for figuring out and for sharing it here :+1:

You using “endpoint” in the URL? That was my issue.