# Unable to listen on http://127.0.0.1:1880/

**URL:** <https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/8018>\
**Category:** General\
**Created:** [15 February 2019 16:32 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/8018 "2019-02-15T16:32:44Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jakell](https://avatars.discourse-cdn.com/v4/letter/j/a183cd/32.png) [@Jakell](https://discourse.nodered.org/u/Jakell)\
**Post date:** [15 February 2019 16:32 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/8018/1 "2019-02-15T16:32:44Z")

</div>

Whenever I try starting up Node-RED in Linux it comes up with this:

 ![node-red](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/3/3ce475968e347e15ce65b04c92ddeb68b28a8616.png)

What can I do to fix this? I've been through every forum that has a similar error, and nothing works or is relatable to my problem. Any help would be greatly appreciated. Thank you for your time!

---

<div class="post-metadata">

**Author:** ![edje11](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/edje11/32/572_2.png) [@edje11](https://discourse.nodered.org/u/edje11)\
**Post date:** [15 February 2019 16:39 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/8018/2 "2019-02-15T16:39:04Z")

</div>

Have a look with **sudo netstat -ltup** what program uses port 1880.  
After that you can decide if the other program or nr can be set to a different port.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [15 February 2019 17:07 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/8018/3 "2019-02-15T17:07:07Z")

</div>

That almost certainly means you already have node-red running. Perhaps you have enabled it to run on boot. You haven't said how you have installed it, but perhaps  
`sudo systemctl status nodered`  
will give a clue.

---

<div class="post-metadata">

**Author:** ![Nic](https://avatars.discourse-cdn.com/v4/letter/n/45deac/32.png) [@Nic](https://discourse.nodered.org/u/Nic)\
**Post date:** [10 April 2020 10:09 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/8018/4 "2020-04-10T10:09:16Z")

</div>

Hi, similar problem here.  
Try to start node-red but the 1880 port is in use, it seems node-red use it. Why am I not able to access the flow using the browser?

root@beaglebone1:/home# sudo netstat -ltup  
Active Internet connections (only servers)  
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name  
tcp 0 0 0.0.0.0:http 0.0.0.0:\* LISTEN 2997/nginx: master  
tcp 0 0 0.0.0.0:domain 0.0.0.0:\* LISTEN 3113/dnsmasq  
tcp 0 0 0.0.0.0:ssh 0.0.0.0:\* LISTEN 2320/sshd  
tcp 18 0 0.0.0.0:1880 0.0.0.0:\* LISTEN 5769/node-red  
tcp6 0 0 [::]:8000 [::]:\* LISTEN 1/init  
tcp6 0 0 [::]:http [::]:\* LISTEN 2997/nginx: master  
tcp6 0 0 [::]:domain [::]:\* LISTEN 3113/dnsmasq  
tcp6 0 0 [::]:ssh [::]:\* LISTEN 2320/sshd  
tcp6 0 0 [::]:3000 [::]:\* LISTEN 1/init  
udp 0 0 0.0.0.0:mdns 0.0.0.0:\* 1861/avahi-daemon:  
udp 0 0 0.0.0.0:domain 0.0.0.0:\* 3113/dnsmasq  
udp 0 0 0.0.0.0:bootps 0.0.0.0:\* 3113/dnsmasq  
udp 0 0 beaglebone1.homenet:ntp 0.0.0.0:\* 2243/ntpd  
udp 0 0 localhost:ntp 0.0.0.0:\* 2243/ntpd  
udp 0 0 0.0.0.0:ntp 0.0.0.0:\* 2243/ntpd  
udp 0 0 0.0.0.0:58269 0.0.0.0:\* 1861/avahi-daemon:  
udp6 0 0 [::]:mdns [::]:\* 1861/avahi-daemon:  
udp6 0 0 [::]:domain [::]:\* 3113/dnsmasq  
udp6 0 0 fe80::caa0:30ff:feb:ntp [::]:\* 2243/ntpd  
udp6 0 0 localhost:ntp [::]:\* 2243/ntpd  
udp6 0 0 [::]:ntp [::]:\* 2243/ntpd  
udp6 0 0 [::]:33204 [::]:\* 1861/avahi-daemon:  
root@beaglebone1:/home#

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [10 April 2020 10:28 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/8018/5 "2020-04-10T10:28:27Z")

</div>

Are you trying to access [http://127.0.0.1:1880](http://127.0.0.1:1880) from the node-red box or an external computer?

127.0.0.1 is not externally accessable.

Have you tried using the actual LAN IP instead?

---

<div class="post-metadata">

**Author:** ![Nic](https://avatars.discourse-cdn.com/v4/letter/n/45deac/32.png) [@Nic](https://discourse.nodered.org/u/Nic)\
**Post date:** [10 April 2020 12:01 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/8018/6 "2020-04-10T12:01:34Z")

</div>

Hi,  
the beagle bone black is in a private network, I use the pc browser to develop the flow and try to connect the beagle bone via browser using the 192.168.x.x IP. The ssh connection on the same IP works properly.  
I tried to disable the node-red start from the boot and in this case I found the init process that occupy the 1880 port.  
I'm confused!  
Thanks

---

<div class="post-metadata">

**Author:** ![Nic](https://avatars.discourse-cdn.com/v4/letter/n/45deac/32.png) [@Nic](https://discourse.nodered.org/u/Nic)\
**Post date:** [10 April 2020 20:09 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/8018/7 "2020-04-10T20:09:57Z")

</div>

Update: after a switch off and on (the simple reboot instruction does not provide the same result) the 1880 port was free. a node-red-stop and then a node-red-start are needed in order to have a right node-red session. Now it is possible to acces at the flow using the browser.  
The next step is adding the beaglebone nodes fouded here: [https://flows.nodered.org/node/node-red-node-beaglebone](https://flows.nodered.org/node/node-red-node-beaglebone)

It seems that a permission issue occures:

root@beaglebone1:/home/debian/node\_modules# npm install node-red-node-beaglebone  
npm WARN checkPermissions Missing write access to /home/debian/node\_modules/node-red-node-beaglebone  
npm WARN enoent ENOENT: no such file or directory, open '/home/debian/package.json'  
npm WARN debian No description  
npm WARN debian No repository field.  
npm WARN debian No README data  
npm WARN debian No license field.

npm ERR! code ELOOP  
npm ERR! syscall access  
npm ERR! path /home/debian/node\_modules/node-red-node-beaglebone  
npm ERR! errno -40  
npm ERR! ELOOP: too many symbolic links encountered, access '/home/debian/node\_modules/node-red-node-beaglebone'

npm ERR! A complete log of this run can be found in:  
npm ERR! /root/.npm/\_logs/2020-04-10T19\_42\_25\_250Z-debug.log

Any advice?  
Thanks a lot

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [10 April 2020 21:17 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/8018/8 "2020-04-10T21:17:54Z")

</div>

The default beaglebone images already come with Node-RED and the necessary nodes - those extra nodes are not necessary. See the docs here - [https://nodered.org/docs/getting-started/beaglebone](https://nodered.org/docs/getting-started/beaglebone)

---

<div class="post-metadata">

**Author:** ![Nic](https://avatars.discourse-cdn.com/v4/letter/n/45deac/32.png) [@Nic](https://discourse.nodered.org/u/Nic)\
**Post date:** [11 April 2020 16:40 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/8018/9 "2020-04-11T16:40:41Z")

</div>

Thank you for your answer dceejay. I am at the beginning (as you proably understood) and I read the docs you linked before my post. At this point: why I am not able to find the beaglebone nodes? They do not appear between the other nodes.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [11 April 2020 17:30 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/8018/10 "2020-04-11T17:30:58Z")

</div>

These are the built in gpio nodes -  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/9/4/94de0c0c616a075d094eb00b18f2b61f6f029a15.png)

---

<div class="post-metadata">

**Author:** ![Nic](https://avatars.discourse-cdn.com/v4/letter/n/45deac/32.png) [@Nic](https://discourse.nodered.org/u/Nic)\
**Post date:** [11 April 2020 19:58 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/8018/11 "2020-04-11T19:58:43Z")

</div>

Ok, I was lookin for these ones: [https://flows.nodered.org/node/node-red-node-beaglebone](https://flows.nodered.org/node/node-red-node-beaglebone)

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [11 April 2020 20:20 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/8018/12 "2020-04-11T20:20:29Z")

</div>

Yes - those are old and no longer supported - so not necessary.

---

<div class="post-metadata">

**Author:** ![Nic](https://avatars.discourse-cdn.com/v4/letter/n/45deac/32.png) [@Nic](https://discourse.nodered.org/u/Nic)\
**Post date:** [12 April 2020 16:42 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/8018/13 "2020-04-12T16:42:50Z")

</div>

Thank you dceejay for your support. I will search for a good guide and will begin the first test; if you have some documents to advise, very welcome...  
thanks.