Just as a test:
What happens if you add the below line to the bottom of /etc/hosts? (you need to reboot after this change) As both resolve to Server: dns.mnd.iss.as9143.net 192.64.119.194 plugins.volumio.org
As I am able to reproduce your error with ip 10.255.20.33
Hi is this ip under volumio’s control, as it doesn’t resolve correctly?
I am able to reproduce this error by adding the below line to my hosts file. 10.255.20.33 plugins.volumio.org
It’s definitely trying to resolve that IP, and on my desktop (without this in hosts) it is also resolving to 192.64.119.194
PING plugins.volumio.org (192.64.119.194) 56(84) bytes of data.
64 bytes from plugins.volumio.org (192.64.119.194): icmp_seq=1 ttl=55 time=163 ms
64 bytes from plugins.volumio.org (192.64.119.194): icmp_seq=2 ttl=55 time=162 ms
I believe that in the background servers are cascaded. So the FQDN is pointing to multiple IP’s. I am able to reproduce your error with 10.255.20.33 plugins.volumio.org, but adding the same line as 192.64.119.194 plugins.volumio.org it works again.
So now I am a bit confused.
They both point to Firebase Cloud functions (which manages the plugins store API), via a Cloudflare worker (to allow people in China and countries where google is blocked to access the plugin store).
This is a very left-field suggestion, however I know that there are sites with STS enabled, and when I put the plugins URL in a browser, it fails to load, as it’s trying to load https://plugins.volumio.workers.dev
But maybe that site doesn’t have https enabled for that domain, and therefore it fails?
I am in Italy. Here are some different curl and ping requests across all those combinations, with the host file that @wheaten suggested.
Well, I use an adblocker on my PC, however on the Pi it’s a base install right out of the manual on your site.
I have a firewall on my network, however it’s not doing anything special or specific, a very standard DROP incoming that are not ACK and that’s about it…
It was working fine until I uninstalled Spotify, as I wanted to update to the latest version to test some of your fixes and it seemed uninstall/re-install is the only way…
OK, I am going to do a full re-build when I get back from a holiday in Puglia. That might just make it go away. Thanks so much both for trying to help, appreciate it!