starred/go-librespot

Fork 0

mirror of https://github.com/devgianlu/go-librespot.git synced 2026-04-26 05:15:49 +03:00

[GH-ISSUE #222] failed retrieving aes key with code 1 #142

New issue

Closed

opened 2026-02-28 14:25:45 +03:00 by kerem · 5 comments

kerem commented

2026-02-28 14:25:45 +03:00

Owner

Originally created by @hillyu on GitHub (Sep 26, 2025).
Original GitHub issue: https://github.com/devgianlu/go-librespot/issues/222

has been working really well until today:
error="failed loading current track (transfer): failed creating stream for spotify:track:1lcBt7LoEikqYmhUoa2cez: failed retrieving audio key: failed retrieving aes key with code 1"

Originally created by @hillyu on GitHub (Sep 26, 2025). Original GitHub issue: https://github.com/devgianlu/go-librespot/issues/222 has been working really well until today: error="failed loading current track (transfer): failed creating stream for spotify:track:1lcBt7LoEikqYmhUoa2cez: failed retrieving audio key: failed retrieving aes key with code 1"

kerem

2026-02-28 14:25:45 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-28 14:25:45 +03:00

Author

Owner

@paradox9955 commented on GitHub (Sep 28, 2025):

Yup. Can confirm it stopped working for me around this time as well.

@paradox9955 commented on GitHub (Sep 28, 2025): Yup. Can confirm it stopped working for me around this time as well.

kerem commented

2026-02-28 14:25:45 +03:00

Author

Owner

@devgianlu commented on GitHub (Oct 3, 2025):

Are you still having this issue? It did not happen to me once since you reported it. Might have been a Spotify issue.

@devgianlu commented on GitHub (Oct 3, 2025): Are you still having this issue? It did not happen to me once since you reported it. Might have been a Spotify issue.

kerem commented

2026-02-28 14:25:46 +03:00

Author

Owner

@paradox9955 commented on GitHub (Oct 3, 2025):

Are you still having this issue? It did not happen to me once since you reported it. Might have been a Spotify issue.

I still have the issue, not able to stream anything while getting this error in the log, whether I use the mobile app, PC/Web app, etc

@paradox9955 commented on GitHub (Oct 3, 2025): > Are you still having this issue? It did not happen to me once since you reported it. Might have been a Spotify issue. I still have the issue, not able to stream anything while getting this error in the log, whether I use the mobile app, PC/Web app, etc

kerem commented

2026-02-28 14:25:46 +03:00

Author

Owner

@kingosticks commented on GitHub (Oct 3, 2025):

Sorry if a stupid question but do you definitely have a premium account? There's apparently some reports elsewhere that indicate Spotify have changed something on their end to lock this endpoint down.

@kingosticks commented on GitHub (Oct 3, 2025): Sorry if a stupid question but do you definitely have a premium account? There's apparently some reports elsewhere that indicate Spotify have changed something on their end to lock this endpoint down.

kerem commented

2026-02-28 14:25:46 +03:00

Author

Owner

@paradox9955 commented on GitHub (Oct 3, 2025):

Sorry if a stupid question but do you definitely have a premium account? There's apparently some reports elsewhere that indicate Spotify have changed something on their end to lock this endpoint down.

Ah that's a bummer. It worked fine without a premium account until a week ago. Thanks anyway though.

@paradox9955 commented on GitHub (Oct 3, 2025): > Sorry if a stupid question but do you definitely have a premium account? There's apparently some reports elsewhere that indicate Spotify have changed something on their end to lock this endpoint down. Ah that's a bummer. It worked fine without a premium account until a week ago. Thanks anyway though.

kerem referenced this issue

2026-02-28 14:26:19 +03:00

[PR #142] [CLOSED] API: Use prior volume updates as a reference for fast relative updates #230

kerem referenced this issue

2026-02-28 14:26:20 +03:00

[PR #144] [MERGED] fix: fix fast relative volume updates #231