# 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/10742>\
**Category:** General\
**Created:** [2 May 2019 08:47 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/10742 "2019-05-02T08:47:39Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![tramanah](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tramanah/32/9122_2.png) [@tramanah](https://discourse.nodered.org/u/tramanah)\
**Post date:** [2 May 2019 08:47 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/10742/1 "2019-05-02T08:47:39Z")

</div>

I am running node red in window 10. Initially, I did setup node-red in the task scheduler on boot up event. I am facing difficulty to view node-red cmd to view my console.log. Therefore I delete task scheduler. But still unable to view console.log because of port in use. But I am able to run node-red in 10.0.0.1:1880

```auto
Welcome to Node-RED
===================

2 May 14:38:14 - [info] Node-RED version: v0.20.3
2 May 14:38:14 - [info] Node.js version: v10.15.3
2 May 14:38:14 - [info] Windows_NT 10.0.17763 x64 LE
2 May 14:38:16 - [info] Loading palette nodes
2 May 14:38:18 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
2 May 14:38:18 - [info] Settings file : \Users\rama_\.node-red\settings.js
2 May 14:38:18 - [info] Context store : 'default' [module=memory]
2 May 14:38:18 - [info] User directory : \Users\rama_\.node-red
2 May 14:38:18 - [warn] Projects disabled : editorTheme.projects.enabled=false
2 May 14:38:18 - [info] Flows file : \Users\rama_\.node-red\flows_DESKTOP-4JCH2MM.json
2 May 14:38:18 - [error] Unable to listen on http://127.0.0.1:1880/
2 May 14:38:18 - [error] Error: port in use

```

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [2 May 2019 09:07 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/10742/2 "2019-05-02T09:07:17Z")

</div>

`netstat -in`  
Check for the 1880 port.

Did you reboot after removing the task from task scheduler ?

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [2 May 2019 09:12 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/10742/3 "2019-05-02T09:12:34Z")

</div>

in the title did you reall mean `http://127.0.0.1.1880` or was that a typo and you meant `http://127.0.0.1:1880`?

---

<div class="post-metadata">

**Author:** ![tramanah](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tramanah/32/9122_2.png) [@tramanah](https://discourse.nodered.org/u/tramanah)\
**Post date:** [2 May 2019 09:15 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/10742/4 "2019-05-02T09:15:46Z")

</div>

yes, i did reboot

---

<div class="post-metadata">

**Author:** ![tramanah](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tramanah/32/9122_2.png) [@tramanah](https://discourse.nodered.org/u/tramanah)\
**Post date:** [2 May 2019 09:16 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/10742/5 "2019-05-02T09:16:03Z")

</div>

Its typo error. Actually its [http://127.0.0.1:1880](http://127.0.0.1:1880)

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [2 May 2019 09:18 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/10742/6 "2019-05-02T09:18:43Z")

</div>

Have you tried using a web browser and seeing what that page contains?

It’s an easy way of eliminating the possibility of node-red is still running on your machine

---

<div class="post-metadata">

**Author:** ![tramanah](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tramanah/32/9122_2.png) [@tramanah](https://discourse.nodered.org/u/tramanah)\
**Post date:** [3 May 2019 09:38 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/10742/7 "2019-05-03T09:38:44Z")

</div>

Hi, I did try on broswer with 10.0.0.1:1880 and 127.0.0.1:1880. Both shows Node-Red Flows. But cmd still persist with the same error after many attempts.

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [3 May 2019 10:02 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/10742/8 "2019-05-03T10:02:05Z")

</div>

So node-red is already running, which is why you get the error

```auto
2 May 14:38:18 - [error] Unable to listen on http://127.0.0.1:1880/
2 May 14:38:18 - [error] Error: port in use

```

because you can't run two copies of Node-RED on the same port.

If you reboot the machine and this happens then it would appear the task scheduler (or something else you have configured such as pm2) is starting Node-RED.

---

<div class="post-metadata">

**Author:** ![tramanah](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tramanah/32/9122_2.png) [@tramanah](https://discourse.nodered.org/u/tramanah)\
**Post date:** [3 May 2019 12:27 UTC](https://discourse.nodered.org/t/unable-to-listen-on-http-127-0-0-1-1880/10742/9 "2019-05-03T12:27:32Z")

</div>

Task Manager or RUN resmon.exe ([https://en.wikipedia.org/wiki/Run\_command](https://en.wikipedia.org/wiki/Run_command)). I did run resmon.exe to monitor Overview tab and Network tab.

In the Overview tab, I am to view node-red is running and able to see port 1880 is active in the Network tab.

I did end task and restart the pc then open cmd and run node-red. It's working.

Thank you to all. Do appreciate most for your support.