Funny crash in API

Hi all,
I have a very funny effect I cannot explain and hope for some help.

I programmed an extension using the official javascript API from roon running of a RaspberryPi zero w with Raspbian.
My core id Win10 and runs the server version of roon, without GUI.
Running the extension anything is fine. Then I start roon on my Win10PC. Aprx. 2.5 min later I see this:


  throw er; // Unhandled 'error' event

Error: connect ETIMEDOUT
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1083:14)
Emitted ‘error’ event at:
at ClientRequest.req.on (/home/pi/rooExtend/node_modules/ws/lib/websocket.js:579:15)
at ClientRequest.emit (events.js:197:13)
at Socket.socketErrorListener (_http_client.js:399:9)
at Socket.emit (events.js:197:13)
at emitErrorNT (internal/streams/destroy.js:82:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
at processTicksAndRejections (internal/process/next_tick.js:76:17)

This did not happen if roon is active on my iPad but starting it on my WinPC i get the crash.

Help would be greatly apreciated because this seems to be a timeout and my application does nothing on port 9100…

Thaks a lot

Ok, now I’ve figured it out for myself!
Apparently not all necessary ports for roon were enabled in my Windows firewall :hot_face:

Now I deleted all the settings for roon that I found in the firewall and then restarted roon. At all the questions of the firewall that appeared, I gave permission for private networks and the error was gone
:grin: :grin: :grin:

1 Like