Radio and Qobuz search end up with a connection issue ( please refresh your page ) most of the time
Describe your network setup
All devices wired to the modem provided by the ISP with 10GB link ( LAN & WAN) I suspect my IP address to be black listed on Cloudfare servers used by Roon , as the issue does not occur if my servers is linked to the mobile network of the same provider ( SFR) or if it is linked to a VPN
Aditional details : I had a change on the ISP side : I used to have a CGNAT address ( shared among other users 10.x.x.x ) and asked to switch to a fullstack IPV4 address 5.x.x.x ( this when the problem started, but it could aslo be a coincidence )
The configuration has always been working perfectly fine before this change, and right now Cloudfare IP’s are the only ones that I’m having trouble with… all my other cloud services hosted on AWS Azur etc are perflectly fine.
Standard fiber optic router provided by ISP, nothing particular. My new static IP address has just been assigned by my ISP and it appeared to be banned from Roon...if I use my mobile connection or a VPN it works... Needless to say it's a fake positive ( my previous unfixed IPs on my fiber modem were working great )
Your post, apart from being a bit alarmist, doesn’t explain what you’re trying to do. I can assure you, Roon has not “banned” your ip. When you’re home, and connected to your home network, Roon Remote should find Roon Server automatically. When you’re away from home, Roon ARC should find your Roon Server automagically, but perhaps with the help of a firewall rule. Away from home, Roon Remote will not work without VPN access to your home network.
If I look at the log file of roon it says unable to connect to 172.67.14.113 socket timeout. the result is that I’m not able to perform any search on the Radio or Qobuz ( album will not be displayed and will not be accessible of course ) and I will end up with a message that says : check you internet connection or " please refresh your page"
If my Roon server is plugged to a VPN I’m not getting the 172.67.14.113 socket timeout error message and all my searches on Qobuz are accomplished in less than a second.
If my Roon server is plugged to my mobile on a LTE or 5G network I’m not getting the 172.67.14.113 socket timeout error message and all my searches on Qobuz are accomplished in less than a second.
If I perform a traceroute to this adress from my LAN ( including a traceroute from the modem itself that does not require a device on the LAN and that does not have any firewall enabled) I can see that the packets are being routed to my ISP network and stopp responding when they are about to reach the cloudfare servers.
Now , once every few hours the connection to this specific server will be established for 2 or 3 seconds and will get terminated by the remote server ( checked with Wireshark )
At first I have thought at a routing issue on the ISP side, I spent an hour with them on the phone , they switch me to same route that my mobile is using ( and for the record it’s working perfectly fine with the mobile ) but it did not work. So it is not a routing issue.
They ( the ISP tech people ) have been doing some test internally from their own servers by spoofing my IP ( while my modem was off of course ) and find out that the packets were rejected by the server… they tried with another IP and it went fine, this confirm that my IP is banned.
So it’s clear that Cloudfare server that Roon is using (at least the server 172.67.14.113) is rejecting my IP I’m not saying it’s roon fault , I 'm juste saying it’s more likely a problem with cloudfare. But of course Cloudfare asked me to deal with Roon
They ( the ISP again ) had previous issues with cloudfare servers randomly blocking specific range of IP with no reason
Ps : there is another post form another user using the ISP than me that run into the exact same issue at the same time and has an IP very close from mine.
I wonder if the issue could be related to your ISP using new DNS servers? We have seen users have a better experience in the past if they change their Router’s DNS servers from the ISP provided ones to Cloudflare DNS, Quad9 or Google DNS. Can you please give this a try and let me know if it helps?
I have been through this article before , the strange thing is that I can ping with no issues at all the servers that belongs to cloudfare and that are close to this IP’s range ( for instance 172.67.14.112 / 172.67.14.114 / 172.67.14.111 etc ) only 172.67.14.113 reject the connection ( and the ping from my landline ip ) and unfortnuatelly it is the server than Roon keeps trying to join.
Regarding my IPV4 , I have tried a dozen of IP checkers , including Honeypot , blacklist check etc , all these online IP checkers report a crystal clean situation ( not even a single doubt about my IP ) , and I not host webservers, mailservers or any other other bandwith consuming activity.
Thank you very much for having a look at my case !
I have tried different DNS ( Cloudfare, Google, Open DNS etc ) but with no success so far.
No matter wich DNS I’m using the same message appear in the log file
11/05 09:58:02 Warn: [easyhttp] [2] POST https://api.roonlabs.net/discovery/1/query web exception without response: socketmsg (TimedOut): Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’hôte de connexion n’a pas répondu. (172.67.14.113:443)
11/05 09:58:02 Warn: [inetdiscovery] failed to query for services ‘com.roonlabs.roonbridge.tcp’ in domains ‘addr:ADDR’: Result[Status=NetworkError]
11/05 09:58:02 Trace: [inetdiscovery] using cache for services ‘com.roonlabs.roonbridge.tcp’ in domains ‘addr:ADDR’
11/05 09:58:40 Warn: messagingservice registration failed: Result[Status=NetworkError]
11/05 09:58:40 Warn: error retrieving lyrics for 52170: NotFound
No matter was done on Roon’s side , my Roon server is now no longer trying to reach 172.67.14.113 ( it was probably replaced by another server ) so now everything is working fluently again , Qobuz search are even faster than before , and I have no more network errors in my log files.
I’m not saying it’s roon fault , I 'm juste saying it’s more likely a problem with cloudfare. But of course Cloudfare asked me to deal with Roon 