search

bbindreiter / node-red-contrib-alexa-remote2-applestrudel

Node-Red Nodes for interacting with Alexa
https://flows.nodered.org/node/node-red-contrib-alexa-remote2-applestrudel
MIT License
74 stars 20 forks source link

ECONNREFUSED working with Alexa #175

Closed gtnscebba closed 3 months ago

gtnscebba commented 5 months ago

I'm using alexa-remote2-applestrudel since last year when I was using Raspberry Bullseye amd NodeRed 3.1.0. Now I use Node Red 3.1.1 on Bookworm. From that moment on, a series of problems have caused an error in Node Red and analyzing the Syslog I see that the palette that Alexa manages is always involved. In particular, the error is always a "Connect Econnrefused" whose IP address (never the same, the last one was 52.16.104.93) is always attributable to Amazonows. I have no other palettes that use AWS beyond Alexa. Node Red goes to "Uncaught Exception": it makes a closure and therefore a restart. This happens in a non -continuous and absolutely random way: in some days it happens 0 times, in others more than once. When it happens, it can be during the day or at night. To avoid these continuous problems, unfortunately I had to totally disable the flow. Since I did it, Node Red has no longer problems. Is it possible to isolate the problem?

Apollon77 commented 5 months ago

Do you have any firewalls or Adblockers on DNS level in place or such? Is DNS setup properly? Because in fact ECONNREFUSED means that an ipwas resolved to an yaddress that did not provided the requested service ... so most likely you always need tocheck whats up. And please also maybe post more detailed errors and stack traces

github-actions[bot] commented 4 months ago

This issue is stale because it has been open for 30 days with no activity.

github-actions[bot] commented 3 months ago

This issue was closed because it has been inactive for 14 days since being marked as stale.