However, Spotify is not content with this & always showed Offline. Since Quad9 is slower for me with my new setup, it was always timing out & PiHole was always responding with the cached lists for Arch's connectivity checks. NetworkManager pings for connectivity checks. Changing that to disabled however broke NetWorkManager for me & I wouldn't want to do that again since I was testing this out in my work laptop. This version checks for connectivity from the /usr/lib/NetworkManager/conf.d/nf file as rightly pointed out by butwhatabout_. The queries which PiHole allowed to passthrough were being queried to Quad9 which for me was slow/timingout.

I had setup Quad9 as my upstream DNS & sadly, Quad9 is damn slow for me with my new ISP. I dug a bit deeper since this was a big bummer for me in addition to Spotify not working. Mine is a 200Mbps connection & strangely the speed dropped to 2Mbps after deploying PiHole. I tried the NetworkManager tip which butwhatabout_ suggested, but sadly that didn't workout for me.įYI: The issue is not with libcurl, infact it doesn't even matter. (I like to block ads, but even if you don't want to block ads, this should still workout for you if you do it properly.) I'm a hardcore user of Arch Linux, I've got about 6 devices running Arch (x86_64 & ARM) & Spotify broke for me in all Arch devices where I had it installed when I redeployed PiHole. Hey yagarea! I had the exact same issue as you, but I've resolved it yesterday.

Spotify for arch linux