If RoonServer isn’t even attempting to initiate a handshake, then the remote discovery process itself is failing. Those device announcements rely on multicast traffic.
What’s the particular network topology serving RoonServer? If you have multiple routers or a mesh network, verify that multicast forwarding and IGMP snooping are both enabled, as these settings often restrict basic multicast traffic when disabled on consumer routers.
If there are managed components in the network path between RoonServer and remote, please list them out to expedite troubleshooting.
Our automatic log requests to the RoonServer instance were acknowledged, but so far the machine hasn’t responded with the logset. It’s possible stateful security features on this network are restricting that traffic - please be sure to safelist Roon’s processes just in case.
In the meantime, please upload a logset here at your convenience. You can use the directions found here and send over a set of logs to our File Uploader.
Sorry the roon support site didnt let me enter enough info. I’m running roon server on ubuntu. I have clients on windows, osx, and andiod they all cycle through the roon logo and “Waiting for your Roon Server”
I’ve reinstalled the server. I’ve reinstalled the clients. On the android client it asked me to log in, then it found the server on my network but it still cycles.
I turned the firewall off on ubuntu. I can SSH to that server fine.
The Roon server logs don’t show anything about a connection attempt:
03/13 15:59:43 Debug: [.NET ThreadPool Worker] [easyhttp] [17] GET to https://api.roonlabs.net/messaging/1/api/messages/e2c2528a-da8a-4515-bbf8-1fb6e1b674cc returned after 173 ms, status code: 200, request body size: 0 B
03/13 15:59:45 Trace: [Broker:Media] [library/compute] computing 1331 / 1331 tracks
03/13 15:59:46 Debug: [.NET ThreadPool Worker] [easyhttp] [18] POST to https://api.roonlabs.net/discovery/1/register returned after 149 ms, status code: 200, request body size: 1 KB
03/13 15:59:46 Trace: [Broker:RoonApi] [inetdiscovery] registered 1 devices, 5 services
03/13 15:59:50 Debug: [.NET ThreadPool Worker] [easyhttp] [19] GET to https://api.roonlabs.net/push-manager/1/connect returned after 175 ms, status code: 200, request body size: 0 B
03/13 15:59:50 Debug: [.NET ThreadPool Worker] [push2] push connector url received from push manager: ws://push-connector-v2-0.prd-roonlabs-1.prd.roonlabs.net/
03/13 15:59:50 Trace: [.NET ThreadPool Worker] [push2] connecting to push2 connector at ws://push-connector-v2-0.prd-roonlabs-1.prd.roonlabs.net/
03/13 15:59:50 Trace: [.NET ThreadPool Worker] [push2] connected to push2 connector at ws://push-connector-v2-0.prd-roonlabs-1.prd.roonlabs.net/
03/13 15:59:52 Debug: [.NET ThreadPool Worker] [easyhttp] [20] POST to https://api.roonlabs.net/device-map/1/register returned after 194 ms, status code: 200, request body size: 2 KB
03/13 15:59:52 Trace: [RemotingServerV2] [devicemap] device map updated
03/13 15:59:57 Info: [7] [stats] 5076mb Virtual, 446mb Physical, 136mb Managed, 265 Handles, 60 Threads
Can you please upload the log set to our servers for review? Typically in cases where the server acknowledges log requests but doesn’t upload it to our servers, there is a firewall blocking proper connectivity. I would suggest double checking the Ubuntu firewall to ensure that Roon is set as an application-level exception.
