Potentially not working in certain areas after recent client update

[Matt17BR]

Potentially not working in certain areas after recent client update

[Matt17BR]

Right, followed those steps but the issue didn't seem to get fixed, I first tried adding both xpui.app.spotify.com and then gew-spclient.spotify.com to the whitelist before building as instructed in readme but that didn't do the trick.

However! What fixed it was whitelisting gew-dealer.spotify.com, api-partner.spotify.com, api.spotify.con After whitelisting the first one alone, I got the hompage and the search function to work. Whitelisting the second one finally provides proper support for the album and artist pages, while the third one makes the queue work again. So that seems to solve the issue. Will try using the client a bit and see if there's any adverse effects, but I doubt so.

[Matt17BR]

@GuessWhatBBQ When testing yesterday I pretty much tested all combinations of those 3 URLs, in order to check what whitelisting each one did and whether anyone was redundant, so no, unfortunately you need all 3. I'll try testing whether whitelisting *dealer works as soon as I'm home though, that does make sense!

[Matt17BR]

@GuessWhatBBQ I can now confirm that everything seems to work as expected by replacing dealer.spotify.com with *dealer.spotify.com on line 37 of the whitelist, as well as adding the two api links mentioned above.

[abba23]

Nice work! I'll just go ahead and add api.spotify.com, api-partner.spotify.com and *dealer.spotify.com to the whitelist.

[abba23]

Thanks for the report. Blocking requests to gew-spclient.spotify.com doesn't break anything for me, so I don't think that's the culprit. I can however see blocked requests to xpui.app.spotify.com in your log, which don't appear in mine.

Since I can't reproduce this myself, you'll have to test it by adding that domain to the whitelist and building yourself. Just follow the build steps in the readme, but add xpui.app.spotify.com to whitelist.h before running make. Then launch Spotify using LD_PRELOAD=./spotify-adblock.so spotify (in the same directory) and see if it works.

[GuessWhatBBQ]

Can confirm the testing by Matt17BR partially. Whitelisting both api-partner.spotify.com and api.spotify.com was required for spotify to be functional, I had the same issues outlined above by Matt17BR. I'm in the South Asia region by the way.

Now regarding the gew-dealer.spotify.com, my guess is that it's specific to Europe West as specified by the gEW at the beginning of the url, and after doing a dns lookup I saw that it has an alias gew-dealer-ssl.spotify.com which is most likely an ssl server. Furthermore it doesnt show up on my logs and the closest thing I could find is dealer.spotify.com which shows up in both our logs as a whitelisted connection, and after doing a dns lookup on dealer.spotify.com it ends up having an alias of global-dealer-ssl.spotify.com most likely another ssl server.

On a side note, after messing around with dns lookups in dig I ended up finding gae-dealer.spotify.com which has an alias gae-dealer-ssl.spotify.com. I'm sure you're noticing a pattern here.

All this makes me believe that your client was facing difficulties with the global server and thus tried connecting to one closer to your region and ended up getting blacklisted as it had a different url pattern than the whitelisted one. This could easily be solved by modifying the whitelist to *dealer.spotify.com, as there is already an entry for it, to account for any such cases in the future.

Testing from @Matt17BR regarding my solution would be appreciated. Also could you try to whitelist just the api urls to see if the issue with the dealer urls was a one off incident ?

Basically revert any changes to the whitelist.h file then add

"api-partner.spotify.com",
"api.spotify.com",

And if that doesnt work just modify "dealer.spotify.com" to "*dealer.spotify.com" at line 37.

[GuessWhatBBQ]

Looks like you've been pretty thorough hehe. Your research definitely saved me from a headache.

[GuessWhatBBQ]

It would be helpful if more people could test the solution before/if it's pushed to master. It's working fine for me now tho, which is better than it was a few hours ago when it was almost unusable.

@abba23 any chance of patching master so we can go back to using the AUR version ? I could open a PR if required