-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Since v1.1 Deezer download gives a network error when Download Fallback option is active. #62
Comments
Please test cooldockerizer93/spotizerr:dev and share logs |
Just tried the dev version (fresh installed) and now it only downloads from Spotify (i see the .ogg files in the downloads folder, regardless if it's using the fallback option or not and both accounts are connected. Also saw the new option for the default service, but only offers the Spotify option.
|
The default services behaviour is intended, just preparing the terrain for long-term thingies. Unfortunately, I currently don't have access to a premium deezer account, so you'll have to wait a while I debug this thing.
Edit: Never mind, I just remembered the api changes made it obsolete. The wait shouldn't be long tho, just a couple of weeks at most |
I got one yesterday lol. Please run
and test that image with the new docker compose file in the repo, in my testings it ran fine. |
I'm running into these issues (only downloading from Spotify while Deezer is configured and fallback enabled). Running 1.2 with the updated docker-compose. Logs don't show any apparant issues:
|
I added proper logging of deezer failures in cooldockerizer93/spotizerr:1.2.1 Please retest and share. |
@Xoconoch could you also please build the arm64 version of your dev/1.2+ containers? Last version I can use is 1.1 |
This is on 1.2.1
So it says my token is wrong. But I double checked the ARL, and that is the right one |
Oops, I confused your arl obfuscation with another common error lol. I would tell you to double check the validity of your account, try downloading directly with the deezer app or smth. If you got your arl through other means note that deezer has implemented a patch that automatically kills over-used arl's. Please clarify if you have access to the actual account (email+psswd) or just the arl so we can further debug this. @RomainBoulay I forgot to add it to the github workflows, done. |
No it's my own ARL! It works perfectly fine in Deemix. But I prefer Spotizerr. I just rechecked the ARL. Now the logs show different errors:
|
I believe I have found the issue, the cooldockerizer93/spotizerr:1.2.1 image wasn't set to be the :latest tag as well. In my testings I was using the 1.2.1 tag directly, that's why I couldn't reproduce it, but once I changed to latest, it happened. Now that I have set that, it should be fine after you run
Just to confirm, what tag were you using in your docker-compose.yaml file? |
Indeed, did a repull and it fixed it! I was using |
Perfect, I will close this issue since your testings confirm that the original error has been also fixed. |
https://[HOST]/api/album/download?service=spotify&url=https%3A%2F%2Fopen.spotify.com%2Falbum%2F0fLhefnjlIV3pGNF9Wo8CD&name=Californication
Even when the service used should be Deezer it still tries for the Spotify URL and throws a 400 HTTP.
Issue is not present when Download Fallback option is not selected and downloads correctly from Spotify only
The text was updated successfully, but these errors were encountered: