Web player stops after playing a song for 9 seconds

[csbubbles]

Spotify web player had worked fine for me for a long while (years), but a couple days ago started pausing playback at 9-second position very consistently. Switching to the next song (pressing the "Next" button) sometimes solves the issue for the next song playback (though, not always), then it happens again. Basically, it completely breaks the user experience, as I can't listen to songs which get stuck at 9 seconds, and have to manually press "Next" every 5-10 minutes.

I cannot see any errors in Chrome's JavaScript console nor any issues with the network requests. Everything is fine with my local network. The issue is only with Spotify's web player, and as far as I can tell, it is something that started happening just recently.

Any advice / help would be much appreciated.

Plan: Free

Country: USA

Device: MacBook Pro 2017

Operating System: macOS Big Sur 11.0.1

Web browser: Chrome 89.0.4389.90

[danth45]

Still not working

[danth45]

@Enigma776  Figured out how to fix this on another post if anyone was wondering.

Change your DNS from cloudflare (1.1.1.1) to anything else google worked for me (8.8.8.8)

[eozthunder]

i hope this is fixed now can i reconnect my spodify now or...

[Wobbled]

Can confirm switching from Cloudflare DNS (to google DNS in my case) resolved the issue.

[ParentalControl]

It’s definitely a DNS resolver issue caused by your Chrome Browser failing to communicate to Spotify or vice versa. It’s apparent when the pause happens at 9 seconds because there is a cpu spike in chrome task manager that’s shows a network cpu process trying to resolve dns within the browser briefly. It only seems to affect Spotify's site other sites don't have this issue. So I would assume there is a issue with Spotify's website programing in the Java scripting or network scripting for the web app when using chrome. This issue doesn't happen on other browsers like Firefox or Edge.

[Emil]

Hello everyone,

due to recent developments, we're again marking this as Fixed.

We've made several backend improvements and from the previous comments those seem to have done the trick for a majority.

For anyone still experiencing this, it looks like the cause is a DNS issue via Chrome - something that's not under our control. All network communication for Spotify goes through the same domain name, so if metadata and playback commands are being sent, the domain is already resolved.

As such, if you're still having issues, please ensure to take the following steps to resolve this:

• Change your default DNS in your network settings - It seems CloudFlare (1.1.1.1) is not an ideal pick, so if you have that one, change it to another DNS provider. Based on reports, Google's (8.8.8.8) is working fine.
• Disable VPN, proxies or ad-blockers - they're not supported and are known to cause playback trouble.
• Switch to a different browser for the Web Player - We've received reports that Firefox and Edge do not experience interruptions. As Edge and Safari are pre-installed on Windows and Mac those are good alternatives to use. If you don't want to make it your default browser, you can just create a custom shortcut for the Spotify Web Player to open in that browser. A good guide on how to do so can be found here.

Shoutout to @danth45 for helping find a solution!

Take care!