Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Issue with the Web Player skipping tracks on multiple devices

We received reports from users having issues with the Web Player skipping tracks after a few seconds of streaming (usually around 10) and occasionally displaying a "Spotify can't play this right now" error.

Hey there folks,
 
We really appreciate all your reports so far!
 
Our tech teams have looked into this, but weren't able to reproduce it. Since this issue could be caused by individual network setups, we'll close this thread as the issue is something that will need to be looked into individually or could get resolved by an overall system and/or functionality change.

 

Here are some troubleshooting steps that are worth taking a look into:


Check if there are any pending updates for your browser and installing them? It's also highly recommended you manually check if the latest version of the Widevine plugin is installed. There's a detailed guide on how to do that in this article.

 

Below you can find some additional things you can try. Click on each section to expand it.

 

Audio Output & Sample Rate

 

Make sure Spotify is mapped to a valid audio device in Windows/macOS and that the sample rate isn’t set too high (anywhere between 44.1 and 192 kHz should be okay). Check “App volume and device preferences” and confirm Spotify is assigned to the correct output. You'll find a detailed guide on how to do that here.

 

USB DACs or external audio interfaces

 

Driver conflicts or odd configuration in advanced setups (e.g., gaming headsets, external DACs) can trigger errors. Disabling/re-enabling the device driver or trying a different USB port often helps.

 

Clearing hosts file

 

Check if the hosts file contains any entries with Spotify in the address and remove them. You'll find the steps to do this here.

 

Symlinks or moved browser data

 

If you moved your browser’s cache/profile via symbolic links, check permissions and confirm Widevine is working with the new location.

 

Firewall/Antivirus software or Ad blockers

 

Aggressive AV or restricted network policies can break DRM or streaming requests. Try disabling them briefly or test with another network. Uninstall any ad-blocker apps.

 

► In case you're using any DJ apps/ software for mixing or creating tunes

 

If you have any DJ apps/software for mixing or creating tunes, try disabling the option to exclusively use a specific sound card. You can try using a different device to verify if the issue is limited to your setup and/ or network.

 


We hope this helps. If you still need a hand, you can start a new topic in the relevant
 Help board including all the steps you've tried so far and their outcome and we'll take it from there.

P.S. If you're on a non-personal device or network (student laptop, student network, corporate laptop, corporate network) get in touch with the administrator for more help! 🙂

Comments
Yordan

Hey folks,

 

Could you check if there are any pending updates for your browser and installing them? It's also highly recommended you manually check if the latest version of the Widevine plugin is installed. There's a detailed guide on how to do that in this article.

 

Below are some additional things you can try. Click on each section to expand it.

 

Audio Output & Sample Rate

 

Make sure Spotify is mapped to a valid audio device in Windows/macOS and that the sample rate isn’t set too high (anywhere between 44.1 and 192 kHz should be okay). Check “App volume and device preferences” and confirm Spotify is assigned to the correct output. You'll find a detailed guide on how to do that here.

 

USB DACs or external audio interfaces

 

Driver conflicts or odd configuration in advanced setups (e.g., gaming headsets, external DACs) can trigger errors. Disabling/re-enabling the device driver or trying a different USB port often helps.

 

Clearing hosts file

 

Check if the hosts file contains any entries with Spotify in the address and remove them. You'll find the steps to do this here.

 

Symlinks or moved browser data

 

If you moved your browser’s cache/profile via symbolic links, check permissions and confirm Widevine is working with the new location.

 

Firewall/Antivirus software

 

Aggressive AV or restricted network policies can break DRM or streaming requests. Try disabling them briefly or test with another network.

 

 

MihailY
Status changed to: Fixed

Hey folks,

 

Thanks for your patience while we looked into this issue.

 

This should now be fixed for everyone. If you're still having trouble, make sure to post a new thread in the relevant help board here.

 

Cheers,

AlienSpooti

Status needs to change back to 'unresolved'.

I just tried it on my systems. All of them are doing the same thing.... plays 1/2 of the first five songs, then 10 seconds of the sixth song, then stops altogether.

stopthelies

this issue is not fixed! why close it down before asking people if it was working? why do spotify mods keep dping this? please get this reopened and get the tech team to do thier job, because my spotify has not worked for 8 months! yes 8 months this has been going on, embarrassing for spotify. keep asking customers to do this and do that, how about your tech team put down the coffee and donuts and look into the issue?  

P-M-T

It's sad, but the problem has been going on for many months. I'm disappointed.

1163280788

This issue is still not solved. On chrome for me it doesnt work, hasnt worked since the end of octorber last year. However it worked and i say worked untill yesterday on my firefox browser. Today on my firefox browser it started doing this issue that it does on my chrome. Spotify have completely lost their touch with their community. How come a multy rich compaty droped the ball so bad on this issue. I am better off listening music on youtube at this point or just go back to good old winap. Set this status back on under investigation.

every time i want to play music on Spotify it keeps saying "spotify can't play this right now' and it keeps skipping the song
emilywaters1996

Hi, this same issue has just started happening on my wep player only as of yesterday. Has the solution from November been overwritten in a later release? Thank you 

GodwinGodwin

 Web Player Stops Playing After 9–10 Seconds and Skips Songs

 

I'm experiencing a persistent issue with the Spotify Web Player here. When I click Play, I often get a message saying "Can't play this song" and it begins skipping down the playlist automatically. After skipping about 5 songs, it eventually plays one, but it only plays for 9–10 seconds before the sound cuts off. Although the audio stops, the progress bar continues moving as if the song is playing, but I don't hear anything.

I've tried Logging out and back in, clearing cache, cookies, and local storage but the issue persists.

Octogone

I have the same issue as the last 6 persons who commented.
There is a real problem that needs to be fixed. It is currently impossible to play Spotify using the Web Player.

 

If this can help fix It. I am using Edge with the last update.
I am also experiencing the same behavior as other after trying:

- Clearing cookies

- Clearing cache

- Disconnecting from every devices

- Clearing cookies again

- Trying incognito mode

 

Important aspect:

 - If I'm connected to other devices, I can control them fine from the web player. But not the inverse, my phone can see it is supposed to be playing on the web player but I do not hear any sound.

- When I start a playlist of a song: It skips 4/5 songs then play for 10 seconds before not having any sound.

- On top of that, at the bottom right, the sound is going to 1% and cannot be moved on the Web Player or even by using a phone. Also, if I manage to make it go up using JS commands, I still do not have sound.

 

Edit:

All my coworkers who have the same web browser but different PC and headset have the same issues.