Roon Api on Build 880: Connection refused error :(

[Geoff_Coupe]

Hard-coding port numbers is a bad idea. Use the discovery method as pointed out by Brian in the post above in this thread:

Roon Api on Build 880: Connection refused error

The port number is not (and was never) a fixed quantity, and Roon API extensions were never intended to hard-code it. It has always been assigned out of a range, where we look for the first available port. 9100 was the first port in that range, so on many machines, Roon would use 9100, but there are many people who have been using 9101 or 9102, and quite a few users who ping-pong around based on the order that various software starts up. We moved the port range because we became aware of sever…