mirror of
https://github.com/devgianlu/go-librespot.git
synced 2026-04-25 21:05:47 +03:00
[GH-ISSUE #188] audio-akp.spotifycdn.com cannot be resolved #122
Labels
No labels
bug
enhancement
pull-request
spotify-side
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/go-librespot#122
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dflvunoooooo on GitHub (Aug 4, 2025).
Original GitHub issue: https://github.com/devgianlu/go-librespot/issues/188
I can not play any music. The service starts fine, but once I try to play a song, nothing happens. The log shows
level=warning msg="failed handling dealer request" error="failed skipping to next track: failed loading current track (advance to spotify:track:6qZthmNcaK0jlrkMZ3khmy): failed creating stream for spotify:track:6qZthmNcaK0jlrkMZ3khmy: failed initializing chunked reader: failed requesting first chunk: Get \"https://audio-akp.spotifycdn.com/audio/67a21f11c15f27bf797847cc95d3680930fa6c15?__token__=exp=1754395379~hmac=72bc83f65a33c021e776549ae69c47255d20cf5fbfc836e4d09ad44a2552e9d7\": dial tcp: lookup audio-akp.spotifycdn.com: no such host. So the problem is resolving audio-akp.spotifycdn.com.Maybe this is related to #175, but I am not sure.
It seems this problem is adressed with librespot-org/librespot with two issues and a solution which is still in progress. librespot issue #1521, librespot issue #4142 and the discussed solution librespot pull request #1524.
Is there a quick workaround?
@devgianlu commented on GitHub (Aug 4, 2025):
Outstading work from Spotify 👍
I'll have to briefly investigate this, will update.
@dflvunoooooo commented on GitHub (Aug 4, 2025):
Thank you for your very fast answer. If I add this to my
/etc/hostsI can use go-librespot@devgianlu commented on GitHub (Aug 4, 2025):
Could you try
github.com/devgianlu/go-librespot@cf27c000d1?@hecht0r commented on GitHub (Aug 4, 2025):
Im not quite sure if it's the same problem but since maybe last week i also have problems playing music.
After
nothing happens...no further logs until the next pongs...
edit: the workaround from @dflvunoooooo works for me
@dflvunoooooo commented on GitHub (Aug 4, 2025):
I will try tomorrow and report back, thank you!
@tooxo commented on GitHub (Aug 5, 2025):
I also have a problem with something that may be related:
Edit: After checking the connection history, go-librespot only seems to try to connect to the first spclient in the list, (even if multiple were fetched) and even after receiving a 5XX from it. Maybe a "timeout" mechanism for dealers/spclients/ap-s should be implemented.
Quick (dirty) fix, that at least gives one the opportunity to restart until it works
diff for fix
@dflvunoooooo commented on GitHub (Aug 5, 2025):
It kinda works. There was a warning in Spotify, that music couldn't be played just now only when I have it locally. But after one or two seconds it worked. Now every time I skip a track or play something else, there is a delay and spotify again warns, that music can't be played, then it starts playing. This does not happen, when the track ends and the next is played automatically.
Here is the log from librespot
Screenshot of Spotifys warning

@iVolt1 commented on GitHub (Aug 6, 2025):
Starting today, I am getting this error that may be related:
time="2025-08-06T09:44:54-05:00" level=warning msg="failed handling dealer request" error="failed loading current track (transfer): failed creating stream for spotify:track:2cPeYxoFd20SPP3VJxg02J: failed getting track metadata: invalid status code from track metadata: 500"
I could not find the location of the complete log so could someone please share that?
@devgianlu commented on GitHub (Aug 6, 2025):
I was waiting for someone to report this. I am having the same issue and currently investigating. Can you open a new issue? See #189
@devgianlu commented on GitHub (Aug 6, 2025):
@tooxo Yours seems to be a different problem, it affects only the spclient stuff by the looks of it. While this one is only for downloading track data. That might be related to changes they have been doing on the backend that ultimately broke bigger stuff like in #189.
@dflvunoooooo That is to be expected unfortunately, because it takes a little bit more time for the request to fail. I don't really like the idea of banning that domain altogether because it may break something if it's the only available.
I would hope that they are fixing this issue and that track fetching works on the first try, even on
audio-akp.spotifycdn.com. So, are you still experiencing delays / failures?@dflvunoooooo commented on GitHub (Aug 7, 2025):
So with version v0.3.2 your fix seems to be implemented. Thank you!
@dflvunoooooo commented on GitHub (Aug 7, 2025):
I feared as much. Is it possible to ban the failing url for one session or for a given time, half an hour for example?
With version v0.3.2 I am still experiencing delays with the same error message within spotify, yes.
@devgianlu commented on GitHub (Aug 7, 2025):
That feels like a good trade off, I'll think about it.
@dflvunoooooo commented on GitHub (Aug 7, 2025):
Awesome, thank you very much!
@devgianlu commented on GitHub (Aug 9, 2025):
@dflvunoooooo I have implemented a qurantine mechanism which will not reuse a given CDN host for 15 minutes if it fails. This should do it!
@dflvunoooooo commented on GitHub (Aug 20, 2025):
This is great, thank you very much! Seems to be working great till now! :)