Dont show node red interface in web browser

I have used node-red in a "raspberry pi" before and it works ok. Now i want to use it in a ubuntu 18.04 OS. I have followed the tutorials in internet, but when i try access through web browser, this cant connect.

Someone knows why it happen?

Start Node-RED

Once Node-RED has started, point a browser at http://(My ip):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

Starting as a systemd service.
30 Jun 03:07:08 - [info]
Welcome to Node-RED

30 Jun 03:07:08 - [info] Node-RED version: v0.20.6
30 Jun 03:07:08 - [info] Node.js version: v10.16.0
30 Jun 03:07:08 - [info] Linux 4.15.0-54-generic x64 LE
30 Jun 03:07:08 - [info] Loading palette nodes
30 Jun 03:07:09 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
30 Jun 03:07:09 - [warn] rpi-gpio : Cannot find Pi RPi.GPIO python library
30 Jun 03:07:10 - [info] Settings file : /home/victor-t/.node-red/settings.js
30 Jun 03:07:10 - [info] Context store : 'default' [module=memory]
30 Jun 03:07:10 - [info] User directory : /home/victor-t/.node-red
30 Jun 03:07:10 - [warn] Projects disabled : editorTheme.projects.enabled=false
30 Jun 03:07:10 - [info] Flows file : /home/victor-t/.node-red/flows_home_melserver.json
30 Jun 03:07:10 - [info] Creating new flow file
30 Jun 03:07:10 - [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.

30 Jun 03:07:10 - [info] Starting flows
30 Jun 03:07:10 - [info] Started flows
30 Jun 03:07:10 - [info] Server now running at

I have resolved it. The problem was with the firewall, you can use sudo ufw allow 1880, and then it works

1 Like