web player stops working with DEVICE_NOT_FOUND error

[sremi]

Plan

Premium

Country

USA

Device

Macbook Pro

Operating System

macOS

My Question or Issue

The web player stops working after a some time when using firefox (version 122): clicking the play button does nothing and the network request shows a 404 error with {"error_type":"DEVICE_NOT_FOUND","message":"Device not found, from edgeproxy"}

This is similar to https://community.spotify.com/t5/Other-Podcasts-Partners-etc/Web-player-error-Device-not-found/m-p/5026481#M72580 but cleaning the cache/cookies/restarting the browser/reloading the page only fixes the problem temporarily.

[Ivelina]

Hey @sremi,

Thanks for posting in the Community!

If you've tried with some troubleshooting steps already, would it be possible to even give it a go on a different web browser? Another step you can also try is to reinstall Firefox and make sure you're running the newest version in order to see if that'll make any difference with Spotify. 

Keep us posted 🙂

[sremi]

Hi Ivelina thank you for your reply! I tried with the web player in Chrome and Safari and ran in the same issue in both after some time with the same error 404 DEVICE_NOT_FOUND. All those browsers are running the newest version.

[Ivelina]

Appreciate the cooperation, @sremi!

Have you by any chance tried with a different internet connection in order to see if that'll change anything? You can restart your router and if it's possible try with sharing mobile data via hotspot.

It's worth mentioning that if you're using a VPN we recommend that you disable it and to try again without it as it can cause different issues with Spotify's performance. 

You could also send us a screenshot or two so we can take a look at the error message you're seeing. You can attach it to your next response by using the Insert image option in the post editor, just make sure not to send any private info.

We'll be on the lookout 🙂

[sremi]

I am not using a VPN.

I am also not able to test with a different internet connection, but if I turn my wifi off and on when running into this issue it goes away. Bizarre. I would rather not have to turn my wifi on and off every time 🙂

I think this may be related? https://bugzilla.mozilla.org/show_bug.cgi?id=1836466#c0

[Ivelina]

Thanks for the update @sremi.

If the error message disappears when you restart the router, then there's most probably some kind of issue with the internet connection and in this situation we think it's best that you check and toggle your router settings and give it some troubleshooting.

In the meantime, the Community's here for you should you need help with anything else 🙂

[sremi]

Hi Ivelina thanks for following up, I have reset my router to the factory default and still having this issue.

Given that no other website ever gave me this error and 1 other person reported having the same problem up top (plus many similar reports on google with Spotify+Device not found) I think this is an issue on Spotify side and not on my side.

[Ivelina]

Thanks for the update, @sremi.

Would it be possible to download the Spotify app either from our website or from the App Store to see if the same error message appears there as well?

If you're still seeing the error message it would be great if you could send us a screenshot so we can take a look.

Keep us in the loop.

[sremi]

I have not seen this issue with the Spotify app (but I have also not used it much). Here is a screenshot of this issue from the Spotify web player from just now.

[Elena]

Hey @sremi, 

Thanks for the screenshot, we`ll take it in account when looking over things. 

Could you please tell us if you experienced any difference when using the downloaded Spotify app from website?

Well be on the lookout!

[sremi]

Any update on this? I am still having this issue with the web player in https://open.spotify.com/.

[AlejaR]

Hey there @sremi,

Thanks for your reply.

In this case, it might be worth clearing your host files. You can do it by following the steps in this article to see if you notice any difference. Since you mentioned that you did not notice issues while using the desktop app, but that you did not use it as much, would you mind sharing with us if within this time you encounter the behavior there? 

Now, we haven't seen similar recent reports on the Community, so we think this might be related to your computer. If the above doesn't do the trick, we'd like to continue gathering info in order to better understand this behavior. Please send us:

• Did you notice if this started to happen after a specific event, such as an OS update?
• Do you use any cache-clearing or task-killing apps? If yes, try setting your browser as an exception.
• Does this happen when using the web player on a different computer? It'd be awesome if you could check.

Keep us in the loop!

[BlueStarBRS]

i have literly now the same error and im very **bleep** i dont have premium just to dont be able to listen too my music on my pc i need my web browser (chrome) and (chromium) to listen with my own equalizer i did everything like him only just dont reset my router.
screenshots

dev console reports <-
browser network tab 

[Susan_GP]

Hi @BlueStarBRS,

Thanks for your reply in this thread.

First up, if you haven't, try clearing your hosts files as @AlejaR suggested. Additionally, were you able to test this with a different internet connection? A mobile hotspot is usually a convenient way to test this.
 

On another note, does Spotify stop working as soon as you start using the Web Player? Or are you able to use it for a while? Did you notice if this happens when clicking something, or looking for something on the Web Player? Or does it happen randomly? 

We'll be here.

[BlueStarBRS]

Ahaha proof that no body have rly checked this issue by the spotify devs it is very simple at least at my point and i explain why:

it is because widewine drm protection isnt running (or the browser components)
(what also explains why nvidea gforce expirience record stops working properly when spotify in browser plays its caused btw by shillty code from the spotify website, on spotify app nvidea moment record works fine but now: back to the topic)

On my device it whas caused by chrome components havent run. this can is caused by the kiosk mode OR like on my end the start parameter: 
--disable-component-update what why ever turns off all components from chrome.

( i used it to force a clean mv2 only browser for future but people recommend everywhere --simulate-outdated-no-au --disable-component-update thats why this faulty command whas in this case here)

on chromium the issue is because i using the "degoogled" chromium what reports on all components 0.0.0.0 ver. that equals to = unavaible

i wanna mention also that my secure boot whas turned off what "can cause" widewine drm dont want run but i wasnt able to verify this issue

you can simply check if the components work with this url in chrome:
chrome://components/

and you NEED widewine (known in the list with: Google Widevine Windows CDM, Widevine Content Decryption Module) in this list if it says 0.0.0.0 or error or is completely missing  in the list you are **bleep** when drm isnt work cuz of bad code from the site it denied the accces to the api and result in an 404 no such device error and you cant play then your music.

also pls SPOTIFY DEV TEAM fix that nvidea moment record freeze when im listen to spotify in my browser you ruined so many nice gameclips form me cuz of this, on the app it is fine so do the same for the browser.

[sremi]

Hi AlejaR, thank you for following up with this issue - that I am still having on macos with both firefox and safari.

I have 3 laptops at home on the same wifi network, 2 macs and 1 linux. I have this same issue with both mac laptops, but somehow I do not have this issue with the linux laptop.

Maybe some weird macos specific config is causing this, none of the 2 macs have any reference to spotify in their host file.

[Eni]

Hey there @sremi, 

Thanks for getting back to us.

We are currently not getting any similar reports and we haven't been able to reproduce the issue, which leads us to believe this might be something caused by some device-specific settings.
 

Rest assured, we'll be on the lookout for more reports about this so we can investigate further. 

If you need a hand with anything else, the Community is here for you.