server logs full of
06/01 14:24:08 Warn: [easyhttp] [811] Post https://device-map.roonlabs.net/1/register web exception without response: Unable to connect to the remote server A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 35.231.208.158:443
06/01 14:24:08 Warn: [easyhttp] [820] Post https://metadata.roonlabs.net/1/performers/translate?c=qobuz-us web exception without response: Unable to connect to the remote server A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 35.231.208.158:443
Seems to be connecting to Qobuz fine, I can see responses with 200 for those, network is fine on the server box.
Restated both Clients and Server without any change
Roon is telling you that it can’t connect to that IP. And pinging it outside of Roon, confirms that you are not able to. As a contrast, I can both ping that IP and tracert it, without issues.
I’d first try 1.1.1.1 for the DNS server as a test.
Are you running just a standard ISP router, or, do you have other stuff like pfsense, pihole, vpn’s working as well? If so, try disabling them.
There is nothing between me and the IP address, I’m using 8.8.8.8 which is googles DNS, so I doubt that’s the issue, the fact it’s resolving to an IP you can ping implies it’s not that.
A traceroute gets onto the main backbone, so it’s not a local issue
1 SC-ENG-CX062F3.mshome.net (172.30.0.1) 0.301 ms 0.278 ms 0.274 ms
2 192.168.2.1 (192.168.2.1) 4.414 ms 4.382 ms 4.513 ms
3 152.44.208.1 (152.44.208.1) 19.820 ms 19.915 ms 19.997 ms
4 174.127.182.4 (174.127.182.4) 19.281 ms 30.063 ms 22.216 ms
5 ae0.br1-woodinville.bb.as11404.net (174.127.141.30) 19.611 ms 19.487 ms 30.203 ms
6 be10.cr1-bds.bb.as11404.net (174.127.137.176) 20.099 ms 29.119 ms 28.943 ms
7 hu0-5-0-20-0.cr2-sea-b.bb.as11404.net (174.127.148.136) 29.237 ms 66.350 ms 66.349 ms
8 be1.cr2-sea-a.bb.as11404.net (174.127.149.136) 21.965 ms 13.732 ms 12.879 ms
9 be55.cr3-sea-a.bb.as11404.net (65.50.198.66) 13.258 ms 21.142 ms 21.818 ms
10 be11.cr5-sea.bb.as11404.net (174.127.151.10) 21.492 ms 20.756 ms 21.285 ms
11 216.243.15.225 (216.243.15.225) 21.980 ms 72.14.198.216 (72.14.198.216) 20.683 ms 22.082 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
The ping times out, possibly something on the way having an issue
I get basically the same dig response, still can’t ping it, probably an issue between me and the server.
Or something on the way deliberately blocking the IP address.