# Start up error - Uncaught Exception

**URL:** <https://discourse.nodered.org/t/start-up-error-uncaught-exception/42588>\
**Category:** General\
**Created:** [13 March 2021 17:18 UTC](https://discourse.nodered.org/t/start-up-error-uncaught-exception/42588 "2021-03-13T17:18:04Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![motley](https://avatars.discourse-cdn.com/v4/letter/m/ee7513/32.png) [@motley](https://discourse.nodered.org/u/motley)\
**Post date:** [13 March 2021 17:18 UTC](https://discourse.nodered.org/t/start-up-error-uncaught-exception/42588/1 "2021-03-13T17:18:04Z")

</div>

On Windows 10 Pro I installed latest version yesterday and managed to get my first flow working, later in the day the PC quietly crashed with NR still running. Today when I try to start NR I get the following messages:

```bash
13 Mar 17:08:14 - [info] Node-RED version: v1.2.9
13 Mar 17:08:14 - [info] Node.js version: v15.11.0
13 Mar 17:08:14 - [info] Windows_NT 10.0.19042 x64 LE
13 Mar 17:08:15 - [info] Loading palette nodes
13 Mar 17:08:16 - [warn] ------------------------------------------------------
13 Mar 17:08:16 - [warn] [node-red-contrib-lorawan-packet-decrypt-nwkey-appkey/lorawan-packet-decrypt-nwkey-appkey] Error: Cannot find module './lora-packet'
Require stack:
- C:\Users\chris\.node-red\node_modules\node-red-contrib-lorawan-packet-decrypt-nwkey-appkey\lorawan-packet-decrypt-nwkey-appkey\lorawan-packet-decrypt-nwkey-appkey.js
- C:\Users\chris\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\registry\lib\loader.js
- C:\Users\chris\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\registry\lib\index.js
- C:\Users\chris\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\runtime\lib\nodes\index.js
- C:\Users\chris\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\runtime\lib\index.js
- C:\Users\chris\AppData\Roaming\npm\node_modules\node-red\lib\red.js
- C:\Users\chris\AppData\Roaming\npm\node_modules\node-red\red.js
13 Mar 17:08:16 - [warn] ------------------------------------------------------
13 Mar 17:08:16 - [info] Settings file : C:\Users\chris\.node-red\settings.js
13 Mar 17:08:16 - [info] Context store : 'default' [module=memory]
13 Mar 17:08:16 - [info] User directory : \Users\chris\.node-red
13 Mar 17:08:16 - [warn] Projects disabled : editorTheme.projects.enabled=false
13 Mar 17:08:16 - [info] Flows file : \Users\chris\.node-red\flows_MotleySim.json
13 Mar 17:08:16 - [error] Uncaught Exception:
13 Mar 17:08:16 - [error] Error: listen EACCES: permission denied 0.0.0.0:1880
    at Server.setupListenHandle [as _listen2] (node:net:1293:21)
    at listenInCluster (node:net:1358:12)
    at doListen (node:net:1496:7)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)

```

Any help gratefully received - I would really like to make NR work.

Chris

---

<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:** [13 March 2021 17:28 UTC](https://discourse.nodered.org/t/start-up-error-uncaught-exception/42588/2 "2021-03-13T17:28:34Z")

</div>

> [@motley](#):
>
> `13 Mar 17:08:16 - [error] Error: listen EACCES: permission denied 0.0.0.0:1880`

This suggests node-red is already running. Have you tried accessing it in the browser?  
`http://localhost:1880`

Or something else is using port 1880

---

<div class="post-metadata">

**Author:** ![motley](https://avatars.discourse-cdn.com/v4/letter/m/ee7513/32.png) [@motley](https://discourse.nodered.org/u/motley)\
**Post date:** [13 March 2021 18:45 UTC](https://discourse.nodered.org/t/start-up-error-uncaught-exception/42588/3 "2021-03-13T18:45:12Z")

</div>

Hi,

Thanks for the reply,

After the pc crashed yesterday it was rebooted and I haven't yet set NR to run automatically so I don't think it's running and [http://localhost:1880](http://localhost:1880) doesn't connect.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [13 March 2021 20:25 UTC](https://discourse.nodered.org/t/start-up-error-uncaught-exception/42588/4 "2021-03-13T20:25:29Z")

</div>

Then first try starting it in safe mode to prevent that other error and see what happens. But do also check to see if anything has grabbed port 1880.

---

<div class="post-metadata">

**Author:** ![motley](https://avatars.discourse-cdn.com/v4/letter/m/ee7513/32.png) [@motley](https://discourse.nodered.org/u/motley)\
**Post date:** [13 March 2021 22:24 UTC](https://discourse.nodered.org/t/start-up-error-uncaught-exception/42588/5 "2021-03-13T22:24:20Z")

</div>

Hi,

Thanks for the reply, I tried node-red --safe and I get the same result, I'm nor sure how to check if anything else is using port 1880, but since it worked yesterday before the crash I suspect there is nothing else on that port.

---

<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:** [13 March 2021 22:39 UTC](https://discourse.nodered.org/t/start-up-error-uncaught-exception/42588/6 "2021-03-13T22:39:10Z")

</div>

Does this pc have hyper v installed? It's know to block allocate ports.

Also what does `netstat -anb` report?

Follow this instructions in [this post](https://stackoverflow.com/questions/48198/how-can-you-find-out-which-process-is-listening-on-a-tcp-or-udp-port-on-windows) to find a process using port 1880.

Lastly, you could try starting node-red with a different port e.g. `node-red -p 18880`

Follow info

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [13 March 2021 23:57 UTC](https://discourse.nodered.org/t/start-up-error-uncaught-exception/42588/7 "2021-03-13T23:57:08Z")

</div>

From PowerShell `Get-Process -Id (Get-NetTCPConnection -LocalPort 1880).OwningProcess`

Or from PowerShell or cmd (as admin): `netstat -a -b`

---

<div class="post-metadata">

**Author:** ![motley](https://avatars.discourse-cdn.com/v4/letter/m/ee7513/32.png) [@motley](https://discourse.nodered.org/u/motley)\
**Post date:** [14 March 2021 08:37 UTC](https://discourse.nodered.org/t/start-up-error-uncaught-exception/42588/8 "2021-03-14T08:37:41Z")

</div>

Hi,

Thanks again for the reply, the netstat -anb (in admin powershell) gives a long list but I see no mention of 127.0.0.1:1880. I do have Vmware Workstation on this PC - for Linux VM testing.

As you suggested I then tried node-red -p 18880 and success ! (a few warnings only).

Out of curiosity I than ran node-red without the -p switch and success again, curious so what ever was on port 1880 yesterday is not there today (I shut this pc down at night).

Either way with thanks to Steve-McI I am back running 🙂

---

<div class="post-metadata">

**Author:** ![motley](https://avatars.discourse-cdn.com/v4/letter/m/ee7513/32.png) [@motley](https://discourse.nodered.org/u/motley)\
**Post date:** [14 March 2021 08:39 UTC](https://discourse.nodered.org/t/start-up-error-uncaught-exception/42588/9 "2021-03-14T08:39:00Z")

</div>

Thanks for the reply, I did try your suggestion and it gives a very informative list and is something I have stored away for future use.

I did have some success - see my other reply 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [13 May 2021 08:39 UTC](https://discourse.nodered.org/t/start-up-error-uncaught-exception/42588/10 "2021-05-13T08:39:17Z")

</div>

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