# Mopidy Spotify not working gstreamer no resource found

**URL:** <https://discourse.mopidy.com/t/mopidy-spotify-not-working-gstreamer-no-resource-found/6324>\
**Category:** Help and support\
**Created:** [August 14, 2026, 11:53am UTC](https://discourse.mopidy.com/t/mopidy-spotify-not-working-gstreamer-no-resource-found/6324 "2026-08-14T11:53:35Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![L\_Hug](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/l_hug/32/2593_2.png) [@L\_Hug](https://discourse.mopidy.com/u/L_Hug)\
**Post date:** [August 14, 2026, 11:53am UTC](https://discourse.mopidy.com/t/mopidy-spotify-not-working-gstreamer-no-resource-found/6324/1 "2026-08-14T11:53:35Z")

</div>

Hi there since two days I can’t stream anything from Spotify while getting an error: gstreamer recourse not found. Has Spotify updated something in their API? Anyone else with this issue?

Thanks

---

<div class="post-metadata">

**Author:** ![jodal](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/jodal/32/2564_2.png) [@jodal](https://discourse.mopidy.com/u/jodal)\
**Post date:** [August 14, 2026, 11:57am UTC](https://discourse.mopidy.com/t/mopidy-spotify-not-working-gstreamer-no-resource-found/6324/2 "2026-08-14T11:57:15Z")

</div>

Yes, Spotify changed something.

You can follow the discussion at [Playback fails with `login5` `INVALID_CREDENTIALS` · Issue #437 · mopidy/mopidy-spotify · GitHub](https://github.com/mopidy/mopidy-spotify/issues/437)

---

<div class="post-metadata">

**Author:** ![L\_Hug](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/l_hug/32/2593_2.png) [@L\_Hug](https://discourse.mopidy.com/u/L_Hug)\
**Post date:** [August 14, 2026, 12:25pm UTC](https://discourse.mopidy.com/t/mopidy-spotify-not-working-gstreamer-no-resource-found/6324/3 "2026-08-14T12:25:44Z")

</div>

Jodal, thanks for the real quick response. As I don’t really understand everything under the link it seems to me that right now there is no solution? Do you think there will be a fix soon?

Thank you for the kind support!

---

<div class="post-metadata">

**Author:** ![L\_Hug](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/l_hug/32/2593_2.png) [@L\_Hug](https://discourse.mopidy.com/u/L_Hug)\
**Post date:** [August 20, 2026, 10:31pm UTC](https://discourse.mopidy.com/t/mopidy-spotify-not-working-gstreamer-no-resource-found/6324/4 "2026-08-20T22:31:39Z")

</div>

Solved it with the help of kingosticks post!

> <https://github.com/mopidy/mopidy-spotify/issues/437#issuecomment-5328412090>
>
> Playback fails with \`login5\` \`INVALID\_CREDENTIALS\` on 5.0.0a3 + gst-plugin-spoti…fy 0.15.0-alpha.1-3aab047 (Premium account, \`streaming\` scope present)
> 
> \### Summary
> 
> Web API works normally (login, playlist refresh). Playback consistently fails: librespot authenticates successfully at the access point, then the \`login5.spotify.com/v3/login\` call returns \`INVALID\_CREDENTIALS\`. Started suddenly on August 10th 2026 on a previously working install; no config changes on my side.
> 
> \### Versions
> 
> \- OS: Raspberry Pi OS Bullseye (armhf, 32-bit), Python 3.9.2
> \- Mopidy 3.4.2 (apt)
> \- Mopidy-Spotify 5.0.0a3 (pip) — pinned by Phoniebox v2 \`requirements-spotify.txt\`; newer releases require Python \>= 3.11 (a4) / \>= 3.13 (a5+), so unreachable on Bullseye
> \- gst-plugin-spotify \`0.15.0-alpha.1-3aab047\` (librespot 0.8.0) — currently the latest published build
> \- Phoniebox v2 (MiczFlor/RPi-Jukebox-RFID)
> 
> \### What I've already verified
> 
> \- Spotify account is \*\*Premium\*\* and active; \`Country: "DK"\`
> \- \`gst-inspect-1.0 spotifyaudiosrc | grep access-token\` → \`access-token : Spotify access token, requires 'streaming' scope\`
> \- Token scopes (from \`\[loglevels\] mopidy\_spotify = debug\`) include \`streaming\`:
> \`playlist-read-private playlist-read-collaborative streaming user-library-read user-follow-read user-library-modify playlist-modify-private playlist-modify-public user-read-recently-played user-read-private user-top-read\`
> \- No \`credentials.json\` anywhere (\`find /var/lib/mopidy /home -name credentials.json\` → empty)
> \- \`client\_id\` / \`client\_secret\` freshly obtained from mopidy.com and present in \`mopidy.conf\`
> \- System clock correct, NTP synced
> \- Outbound TCP 4070 reachable (\`nc -zv ap-gew4.spotify.com 4070\` succeeds)
> \- Confirmed 5.0.0a3 does call \`source.set\_property("access-token", ...)\` in \`backend.py\`, so the token is being handed to the plugin
> 
> \### Log (debug)
> 
> \`\`\`
> INFO mopidy\_spotify.web Logged into Spotify Web API as \<user\>
> INFO mopidy\_spotify.playlists Refreshed 5 Spotify playlists
> DEBUG mopidy\_spotify.web Token scopes: ... streaming ...
> INFO spotifyaudiosrc Using librespot 0.8.0
> DEBUG librespot hyper\_rustls::config: with\_native\_roots processed 150 valid and 0 invalid certs
> DEBUG librespot\_core::connection: Authenticating with AP using AUTHENTICATION\_SPOTIFY\_TOKEN
> DEBUG librespot\_core::connection: Authenticating with AP using AUTHENTICATION\_STORED\_SPOTIFY\_CREDENTIALS
> INFO librespot\_core::session: Authenticated as '\<user\>' !
> DEBUG librespot\_core::login5: new Login5Manager
> DEBUG librespot\_core::http\_client: Requesting https://login5.spotify.com/v3/login
> ERROR librespot\_playback::player: Unable to load audio item: Error { kind: FailedPrecondition, error: FaultyRequest(INVALID\_CREDENTIALS) }
> ERROR spotifyaudiosrc imp.rs:278 \<source\> track is not available
> ERROR mopidy.audio.gst GStreamer error: Resource not found.
> \`\`\`
> 
> \### Question
> 
> Note the auth sequence: it attempts \`AUTHENTICATION\_SPOTIFY\_TOKEN\`, immediately falls through to \`AUTHENTICATION\_STORED\_SPOTIFY\_CREDENTIALS\`, and that succeeds — despite no credentials cache existing on disk. Is the access token actually being used for the AP handshake here, or is the token path silently failing before \`login5\` is reached?
> 
> This looks closely related to librespot-org/librespot#1660 (same \`login5\` rejection after successful AP auth), which was reported as reproducing on Bullseye, Bookworm and Trixie alike.
> 
> Happy to provide full unfiltered logs or test patches.

Thank you guys for your work on Mopidy and your help! I really appreciate it!

---

<div class="post-metadata">

**Author:** ![system](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/system/32/1_2.png) [@system](https://discourse.mopidy.com/u/system)\
**Post date:** [August 23, 2026, 10:32pm UTC](https://discourse.mopidy.com/t/mopidy-spotify-not-working-gstreamer-no-resource-found/6324/5 "2026-08-23T22:32:07Z")

</div>

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.