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.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
Extra context: In the screenshot of the browser console, you can see a console.log("page is loaded now"). I put that there when the page finished loading, and directly after i clicked play on one of the playlists on the home screen. The yellow "source map error" right after the console.log happened before i clicked play. I'm not using any "privacy" or ad blocking plugins on the spotify web player. i have ublock origin installed, but spotify is whitelisted.
Hi there @ExperimentalCyborg,
Thanks for reaching out. Is there any pattern as to when this happens and when it doesn't or is it purely intermittent? Also, does it happen on other browsers such as Chromium?
Let us know how it goes.
I have not detected a pattern so far. I'll switch browsers for a while and report back when it happens in chromium as well.
Thanks for your reply.
Take your time to test it out. We'll be here.
Cheers!
I've been alternating between Chromium and FireFox every other day, and it seems that this issue does not happen on Chromium.Something very interesting though is that if the bug happens on FF, playing some Spotify music through Chromium even for a second will make FF start working too. I doubt it has something to do with DNS caching since both browsers use a different DNS service, FF is configured to use Cloudflare. while Chromium is using whatever is the default for it (Google or my ISP, i'm not sure). I will configure FF DNS to use my ISP and I'll report back if Cloudflare caused some weird issues somehow.
TL;DR it seems there's a weird interaction between FireFox and either the DNS, the network path or Spotify CDN. Not sure which yet.
The thing where chromium plays also fixed Firefox plays stopped working, it might have been a fluke. Firefox is giving me
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://seektables.scdn.co/seektable/f9a92c9769e1384104a9aaad8148ff23bfc77f21.json. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 400.
these CORS errors again.
To me it seems like one of the CDN routes/servers is misconfigured and Chrome is simply less strict than Firefox when it comes to CORS.
Still a problem on firefox 123.0 (64-bit)
Hello @ExperimentalCyborg,
Thank you for taking the time to troubleshoot and for letting us know of your findings.
We agree that this seems to be some type of issue in the set up around Firefox. We have spotted that the issue does seem to be intermittent according to most reports that we have gotten and can get resolved by starting playback on a different device or browser.
We'd advise to keep the browser up to date as to not miss any updates on the functionality of Spotify web.
Cheers.
Hey there you, Yeah, you! 😁 Welcome - we're glad you joined the Spotify Community! While you here, let's have a fun game and get…