Failed fetching audio key! gid: 05058228a13f40ed98603c6982a3a1fc, fileId: 52c8e85dd897edc8b121bd556820c62f027ab403 #25
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Investigation
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
spotizerrphoenix/spotizerr-phoenix#25
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?
Describe the bug
I have just installed the latest version of the docker image, used a premium spotify account, and setup the latest auth.
However, when I try to download a song I get this error:
Last error: Failed fetching audio key! gid: 05058228a13f40ed98603c6982a3a1fc, fileId: 52c8e85dd897edc8b121bd556820c62f027ab403
Have I done something wrong, is anyone else getting this error?
To Reproduce
try to download a song after docker running on 7171.
Expected behavior
The song to download.
Desktop (please complete the following information):
docker-compose.yaml
.env
Logs
you can try upgrading to the latest version of spotizerr-phoenix and reauthenticating with the latest spotizerr-auth-phoenix tool to see if that helps with your issue
Hello,
I have the same issue, I have a Spotify premium account with the 3 months trial (not sure if that's related). I can confirm that upgrading to the latest version of spotizerr-phoenix and reauthenticating with the latest spotizerr-auth-phoenix did not solve the issue for my case
@Puya_Puya wrote in #25 (comment):
thanks for the response. that's interesting. its completely possible to the trial may have something to do with it
just out of curiosity, if you set LOG_LEVEL=DEBUG in your spotizerr-phoenix's env / docker compose are you able to see logs for
[DEBUG] Parsed product info:for example:
checklist:
Clear Site Data