Download no longer works (Spotify) #16
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
Download via Spotify no longer works.
To Reproduce
Precise steps to reproduce the behavior (start from how you built your container):
Expected behavior
Successful download.
Screenshots
Desktop (please complete the following information):
docker-compose.yaml
.env
Config
Logs
Version
Downloads still work for me on v3.3.0. #14 has information if you want to try and downgrade.
@mcn18 wrote in #16 (comment):
I downgraded to v3.3.0, but downloading is still not working.
I also applied the fix from spotizerr/librespot-spotizerr#1 to v3.3.0 after downgrading, but downloading still returns the
Audio key error, code: 1. I have also noticed that similar projects are facing the same issue.v3.3.0 logs
v3.3.0 logs after applying the fix from spotizerr/librespot-spotizerr#1
@Krunox wrote in #16 (comment):
You might have to try a semi-fresh install of spotizerr. Try deleting the data folder where your compose file is and then go through the setup with spotizerr-auth. Applying my fix on 3.3.0 wouldn't make a difference because as far as I know that fix only corrects what's broken in 4.0.
I might be mistaken about the downgrade being 100% compatible (had fully uninstalled to test deemix then reinstalled spotizerr 3.3.0). I re-setup using spotizerr-auth the same day I wrote #14 and haven't had any connectivity issues since.
I don't know what the deal is with 4.0.0 and credential errors. I presume it's something with
It also should put a final solution to rate limits, since we now only use the spotify webapi for searching, everything metadata-related is done through librespot, which seems to be completely free of any rate limits.as was said in the 4.0.0 release notes.Regardless, 3.3.0 has been stable for me on a fresh install. I was even able to keep the download history intact upon switching. Let me know if resetting the data folder works for you.
@mcn18 wrote in #16 (comment):
I did a fresh install twice. I recreated the directories and the .cache file, I even removed the Redis volume, but still no luck downloading anything.
My best guess is... I'm probably being rate-limited, so I'll try the download again in a few days. I will update here if it works then.
I've already enabled real-time downloading, but it doesn't seem to do anything. I was trying to download more than 100 tracks at once, but the real-time downloading wasn't working lol
@mcn18 I bought Spotify Premium, and now the download works again. The download does not work on any of my Spotify Free accounts.
It seems they may have enforced restrictions on Spotify Free accounts.
Also, I can confirm that spotizerr-auth no longer works with v4.0.0. #14
yoo @Krunox
not working for me even on the previous version and with spotify premium
Original error: Maximum retry limit reached#18
any ideas here?
@yeewhothis Spotify updated their endpoints, and no one is maintaining this anymore.
librespot-python already fixed this, you can see them here.
Hey, I created a for with to fix this issue here:
fameless5/librespot-spotizerr@9512ec5a6cHowever I don't know how to get all te dependencies working in order for spotizerr to work, could someone help me on that ? (Or tag the owners so they can accept the merge => merge request here : spotizerr/librespot-spotizerr#3)
@fameless5 The owner is unlikely to merge it as this project has been abandoned, so it would be best if you forked it and applied the fix there instead
@Krunox wrote in #16 (comment):
so just to understand the fix, librespot-spotizerr's python package needs to be updated to support the new endpoints, and then the spotizerr image would need to be updated too?
@Krunox @fameless5 @yeewhothis
i've decided to take on the maintenance of spotizerr through
spotizerr-phoenix: #19https://lavaforge.org/spotizerrphoenix
just update your docker image to:
spotizerrphoenix/spotizerrand it should work again like it used to
@spotizerrphoenix wrote in #16 (comment):
YES, it's working for me again! thank you so much 🚀