Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Cheers,
with some more or less recent update to the open.spotify.com player, Spotify stopped working for me (Firefox).
Browsing Spotify works perfectly fine but anytime I press the play button nothing happens, meaning no music is played and the time indicator remains at 0:00.
As it turns out from the console logs and web-player.js, Spotify tries to connect to Google in order to use their recaptcha service to verify I'm not a robot. This does not work because I'm blocking requests to Google while on Spotify.
And to be honest, why shouldn't I?
My question is, are you planning on keeping this "feature"? Is it really necessary to have recaptcha "verification" on the play button even though a user is logged in?
Kind regards,
Markus
ps: ffs, even posting this message requires recaptcha >.<