# Help with errors

**URL:** <https://discourse.nodered.org/t/help-with-errors/86194>\
**Category:** General\
**Created:** [6 March 2024 16:07 UTC](https://discourse.nodered.org/t/help-with-errors/86194 "2024-03-06T16:07:29Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![IanI](https://avatars.discourse-cdn.com/v4/letter/i/cdc98d/32.png) [@IanI](https://discourse.nodered.org/u/IanI)\
**Post date:** [6 March 2024 16:07 UTC](https://discourse.nodered.org/t/help-with-errors/86194/1 "2024-03-06T16:07:29Z")

</div>

I usually run Node-Red (3.1.6) (Node.js 20.11.1) as a service in Windows and so don't see the startup log. Today I had occasion to run from the command line and saw the following;

```auto
Unhandled rejection Error: No sockets available, cannot start.
    at SSDP._createSockets (C:\Users\Ian\.node-red\node_modules\node-ssdp\lib\index.js:186:11)
    at SSDP._start (C:\Users\Ian\.node-red\node_modules\node-ssdp\lib\index.js:229:10)
    at C:\Users\Ian\.node-red\node_modules\node-ssdp\lib\server.js:79:10
    at Promise._execute (C:\Users\Ian\.node-red\node_modules\bluebird\js\release\debuggability.js:384:9)
    at Promise._resolveFromExecutor (C:\Users\Ian\.node-red\node_modules\bluebird\js\release\promise.js:518:18)
    at new Promise (C:\Users\Ian\.node-red\node_modules\bluebird\js\release\promise.js:103:10)
    at SsdpServer.start (C:\Users\Ian\.node-red\node_modules\node-ssdp\lib\server.js:72:10)
    at new AmazonEchoHubNode (C:\Users\Ian\.node-red\node_modules\node-red-contrib-amazon-echo-aller\nodes\amazon-echo-hub.js:19:18)
    at Object.createNode (C:\Users\Ian\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\runtime\lib\flows\util.js:182:27)
    at Flow.start (C:\Users\Ian\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\runtime\lib\flows\Flow.js:261:54)
    at async Object.start [as startFlows] (C:\Users\Ian\AppData\Roaming\npm\node_modules\node-red\node_modules\@node-red\runtime\lib\flows\index.js:403:17)

```

Any help in resolving these gratefully accepted.

---

<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:** [6 March 2024 16:43 UTC](https://discourse.nodered.org/t/help-with-errors/86194/2 "2024-03-06T16:43:30Z")

</div>

> [@IanI](#):
>
> ```auto
> at new AmazonEchoHubNode (C:\Users\Ian\.node-red\node_modules\node-red-contrib-amazon-echo-aller\nodes\amazon-echo-hub.js:19:18)
> 
> ```

node-red-contrib-amazon-echo-aller is your issue - a node that does not correctly handle its errors.

It seems [node-red-contrib-amazon-echo-aller](https://flows.nodered.org/node/node-red-contrib-amazon-echo-aller) has not been updated in 3 years, 8 months and the github repository shows it to be a fork of an even older node.

Normally, I would recomend that you contact the author by the repository issues page but [that repository](https://github.com/allerallegro) has issues disabled.

You may wish to change to one of the more up-to-date alexa nodes (I dont use alexa/amazon products, so cannot recommend any)

In the mean time, you can start node-red on the command line with the `--safe` flag

---

<div class="post-metadata">

**Author:** ![IanI](https://avatars.discourse-cdn.com/v4/letter/i/cdc98d/32.png) [@IanI](https://discourse.nodered.org/u/IanI)\
**Post date:** [6 March 2024 16:56 UTC](https://discourse.nodered.org/t/help-with-errors/86194/3 "2024-03-06T16:56:02Z")

</div>

Thank you. I removed [node-red-contrib-amazon-echo-aller] and the errors have gone. I owe you a coffee 🙂

---

<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:** [20 March 2024 16:56 UTC](https://discourse.nodered.org/t/help-with-errors/86194/4 "2024-03-20T16:56:09Z")

</div>

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