Roon no longer starts after 10 days of non-use [Solved - Port issue due to WiFi + Transfer program]

[Bill_Janssen (Wigwam wool socks now on asymmetrical isolation feet!)]

Yes, in this particular case. But not in general.

[Andreas_Philipp1]

This post is about the port range used for the extension API. This has nothing to do with the problem experienced by the OP.

This was the problem:

04/22 15:15:07 Warn: [multicastreceiver] couldn’t bind to iface 169.254.187.211:1900, message: Une tentative d’accès à un socket de manière interdite par ses autorisations d’accès a été tentée
04/22 15:15:07 Warn: [multicastreceiver] couldn’t bind to iface 192.168.1.21:1900, message: Une tentative d’accès à un socket de manière interdite par ses autorisations d’accès a été tentée
04/22 15:15:07 Warn: [multicastreceiver] couldn’t bind to iface 127.0.0.1:1900, message: Une tentative d’accès à un socket de manière interdite par ses autorisations d’accès a été tentée

It is now clear that a third-party software has already bound to port 1900, so Roon’s ‘multicast receiver’ failed.

Edit: In fact this is a little more intricate… at the moment when ‘multicast receiver’ tries to bind to port 1900 of all identified network interfaces, Roon doesn’t fail. Notice that in the log it shows a warning, not an error. It fails some time later, when Roon tries to open a socket connection on the interfaces. Then it throws an exception and logs an error, because before opening a socket connection it must have bound to the respective network interface.

So ‘multicast receiver’ could bind to another fail-over port, when it finds that it cannot bind to port 1900. And, of course, the code which is executed later at the moment of establishing the socket connection must then be notified that it cannot open the connection on port 1900 but on fail-over port…