spotizerrphoenix/spotizerr-phoenix

Fork 6

Downloads stopping #17

New issue

Open

opened 2025-12-14 11:57:24 +00:00 by schoenfbe · 3 comments

schoenfbe commented

2025-12-14 11:57:24 +00:00

Hi, I have had some success with spotizerr a couple weeks ago, but then started running into issues with downloads aborting/pausing indefinitely.

I have yesterday setup a new k3s cluster and also setup spotizerr, setup and authentication were without issues and I could also find my playlists and start download, I immediately saw some songs downloaded, but then it stalled and I don't know why.
I had the same issue on the previous setup which was just with docker compose, so I don't think it's the setup.
My spotify account is currently premium and also not banned, might be some rate limiting issues tho, but I think spotizerr has some issue and I can't figure out what.
I authenticated through spotify on my phone and that seemed to work without problems, at least some downloads worked so the auth has to be fine I think.
Can't link the yaml so uploaded the deployment as txt.

I'll append the logs from spotizerr & redis as well as some screenshots.

Thanks for any help, cheers!

Hi, I have had some success with spotizerr a couple weeks ago, but then started running into issues with downloads aborting/pausing indefinitely. I have yesterday setup a new k3s cluster and also setup spotizerr, setup and authentication were without issues and I could also find my playlists and start download, I immediately saw some songs downloaded, but then it stalled and I don't know why. I had the same issue on the previous setup which was just with docker compose, so I don't think it's the setup. My spotify account is currently premium and also not banned, might be some rate limiting issues tho, but I think spotizerr has some issue and I can't figure out what. I authenticated through spotify on my phone and that seemed to work without problems, at least some downloads worked so the auth has to be fine I think. Can't link the yaml so uploaded the deployment as txt. I'll append the logs from spotizerr & redis as well as some screenshots. Thanks for any help, cheers!

spotizerr-redis.log

9 KiB

spotizerr.log

32 KiB

spotizerr-deployment.txt

3.5 KiB

Screenshot 2025-12-14 125528.png

44 KiB

Screenshot 2025-12-14 125418.png

50 KiB

Screenshot 2025-12-14 124434.png

130 KiB

spotizerrphoenix commented

2025-12-16 23:58:22 +00:00

Owner

hey @schoenfbe!

Based on your screenshots and logs you could be rate limited. the symptoms you mentioned happen to me after rate limited / not enabling/adjusting realtime

Few things you can try:

Enable/Adjust Realtime downloading & Reduce Max Concurrent Downloads

i noticed you have realtime downloading off
try enabling it and setting the real time speed multiplier to 10
also lower your max concurrent downloads to: 3
you probably want to mess around with those numbers but i would suggest a realtime multiplier of 10 and max concurrent of 3
you might need/want to restart your spotizerr service after updating/saving config
this will slow down your downloads but simulate realtime downloads of tracks so it's not over requesting for tracks

Reauthenticate with the new spotizerrphoenix/spotizerr-auth

sounds like you did already but just to verify in case you haven't already

Probably Unrelated:

i see you're running 4.0, at any point did you try updating your spotify api creds?
although unlikely, i ask this because prior to the current latest v4.0.14:
there was a bug where the spotify api creds was not being saved to the correct location (search.json)
- although i believe 4.0 should have the new changes
so if you updated your api creds prior / revoked your previous creds - you may still be using your previous creds
after updating spotizerrphoenix:spotizerr:latest, you may need to clear cache and reload the page
- then make sure to save the correct api creds on the config page again
you can also verify this is correct by going to your volume mount: data/creds/search.json

let us know if any of those help in case it can help other users as well

hey @schoenfbe! Based on your screenshots and logs you could be rate limited. the symptoms you mentioned happen to me after rate limited / not enabling/adjusting realtime Few things you can try: **Enable/Adjust Realtime downloading & Reduce Max Concurrent Downloads** - i noticed you have realtime downloading off - try enabling it and setting the real time speed multiplier to 10 - also lower your max concurrent downloads to: 3 - you probably want to mess around with those numbers but i would suggest a realtime multiplier of 10 and max concurrent of 3 - you might need/want to restart your spotizerr service after updating/saving config - this will slow down your downloads but simulate realtime downloads of tracks so it's not over requesting for tracks **Reauthenticate with the new `spotizerrphoenix/spotizerr-auth`** - sounds like you did already but just to verify in case you haven't already **Probably Unrelated:** - i see you're running `4.0`, at any point did you try updating your spotify api creds? - although unlikely, i ask this because prior to the current latest v4.0.14: - there was a bug where the spotify api creds was not being saved to the correct location (`search.json`) - although i believe `4.0` should have the new changes - so if you updated your api creds prior / revoked your previous creds - you may still be using your previous creds - after updating `spotizerrphoenix:spotizerr:latest`, you may need to clear cache and reload the page - then make sure to save the correct api creds on the config page again - you can also verify this is correct by going to your volume mount: `data/creds/search.json` let us know if any of those help in case it can help other users as well

schoenfbe commented

2025-12-20 12:08:33 +00:00

Author

Hi @spotizerrphoenix, thanks for the response!

Yeah I thought so too, but adjusting the concurrency and/or also switching to realtime (with cooldown time inbetween, tho I don't know how much that would be, maybe you'd know?) the issue remained.

I was then running with a realtime multiplier of 2-3 and a concurrency of 3-5, but that didn't change.
(I also changed to "latest", but I didn't re-authenticate, I might try that!

I will try the settings you suggested with restarting, but my spotify premium has run out this week and I'm afraid that then lets me no longer download via spotify right? at least logs show that everything now falls back to deezer and spotify doesn't seem to work, so for now I can't test that further :/

what I did notice was that that problem seems to be only related to downloading playlists, trying individual songs or even artist discographies seems to work flawlessly (now only through deezer, but before also with spotify)

I have setup everything through your spotizerr/spotizerr-auth, but I am not home over the holidays so I don't know if I can re-authenticate at the moment since it seems the spotify instance that authenticates has to be in the same network no? trying to setup rdp on my homelab and install spotify there so I can have an "On-network" instance for auth, that should help.
My previous workflow was to just accept the connection via my pc/laptop/phone hanging in the same network as my homelab when home, but I've read in some thread that it should be the same machine, could that be an issue? I thought not since it's only for auth, everything else should be fine?

your "prob unrelated" points:

no, I am using the same api creds the whole time, those are active for ~3 years now, I could try generating new ones if you think that might help?
I will check that, I think it managed auth fine tho, but might be!
the saved credentials under data/creds/search.json are the correct ones, same as in my spotify developer dashboard, should be fine
I'll try with updating and clearing the cache, I presume you mean ~/spotizerr/cache ? (that dir seems to be empty anyway, which seems weird, same with .cache.backup)

if you have any further suggestions, I'm all open for em, got some time to play now :)

update: I've managed to install (well, that wasn't the issue) and access spotify on my homelab and have a gui via rdp despite it being headless, so I can try to re-authenticate, and this time it'd indeed be the same physical machine, except if it makes some difference that spotify is running on baremetal and spotizerr in k3s? spotizerr-auth tho will also just run via docker on baremetal

update 2: I've seen you pushed 4.0.15 and updated to that, I did not change anything else (also no new auth), so far it seems to work well, I've downloaded 2 small playlists (12 & 29 songs each), the first worked flawlessly, the second failed some songs, but all else downloaded from spotify in .flac, so my account no longer being premium doesn't seem to matter.
one issue might have been me provisioning to few resources, I got some failed API calls and unresponsive server, apparently spotizerr crashes before kubernetes can allocate the additional resources, I've now set it to request 1GB RAM and 1.5CPUs, that seems like overkill since it only uses 405m CPUs and ~450MB RAM, but whatever, and now it seems to work way better.

I currently can't replicate the issues I had with playlists stalling, so far it's downloading fine, I'll monitor it tho :)

sidenote: awesome work :D

Hi @spotizerrphoenix, thanks for the response! Yeah I thought so too, but adjusting the concurrency and/or also switching to realtime (with cooldown time inbetween, tho I don't know how much that would be, maybe you'd know?) the issue remained. I was then running with a realtime multiplier of 2-3 and a concurrency of 3-5, but that didn't change. (I also changed to "latest", but I didn't re-authenticate, I might try that! I will try the settings you suggested with restarting, but my spotify premium has run out this week and I'm afraid that then lets me no longer download via spotify right? at least logs show that everything now falls back to deezer and spotify doesn't seem to work, so for now I can't test that further :/ what I did notice was that that problem seems to be only related to downloading playlists, trying individual songs or even artist discographies seems to work flawlessly (now only through deezer, but before also with spotify) I have setup everything through your spotizerr/spotizerr-auth, but I am not home over the holidays so I don't know if I can re-authenticate at the moment since it seems the spotify instance that authenticates has to be in the same network no? trying to setup rdp on my homelab and install spotify there so I can have an "On-network" instance for auth, that should help. My previous workflow was to just accept the connection via my pc/laptop/phone hanging in the same network as my homelab when home, but I've read in some thread that it should be the same machine, could that be an issue? I thought not since it's only for auth, everything else should be fine? your "prob unrelated" points: - no, I am using the same api creds the whole time, those are active for ~3 years now, I could try generating new ones if you think that might help? - I will check that, I think it managed auth fine tho, but might be! - the saved credentials under data/creds/search.json are the correct ones, same as in my spotify developer dashboard, should be fine - I'll try with updating and clearing the cache, I presume you mean ~/spotizerr/cache ? (that dir seems to be empty anyway, which seems weird, same with .cache.backup) if you have any further suggestions, I'm all open for em, got some time to play now :) update: I've managed to install (well, that wasn't the issue) and access spotify on my homelab and have a gui via rdp despite it being headless, so I can try to re-authenticate, and this time it'd indeed be the same physical machine, except if it makes some difference that spotify is running on baremetal and spotizerr in k3s? spotizerr-auth tho will also just run via docker on baremetal update 2: I've seen you pushed 4.0.15 and updated to that, I did not change anything else (also no new auth), so far it seems to work well, I've downloaded 2 small playlists (12 & 29 songs each), the first worked flawlessly, the second failed some songs, but all else downloaded from spotify in .flac, so my account no longer being premium doesn't seem to matter. one issue might have been me provisioning to few resources, I got some failed API calls and unresponsive server, apparently spotizerr crashes before kubernetes can allocate the additional resources, I've now set it to request 1GB RAM and 1.5CPUs, that seems like overkill since it only uses 405m CPUs and ~450MB RAM, but whatever, and now it seems to work way better. I currently can't replicate the issues I had with playlists stalling, so far it's downloading fine, I'll monitor it tho :) sidenote: awesome work :D

spotizerrphoenix commented

2025-12-20 21:46:57 +00:00

Owner

hey @schoenfbe thanks for the update

good to hear it's working for you now. hard to tell but generally looked like a rate limiting issue

might be good to stop/restart your containers, hold back on downloads for a day, and try with the proposed real time/concurrency settings to see if that helps

update: I've managed to install (well, that wasn't the issue) and access spotify on my homelab and have a gui via rdp despite it being headless, so I can try to re-authenticate, and this time it'd indeed be the same physical machine, except if it makes some difference that spotify is running on baremetal and spotizerr in k3s? spotizerr-auth tho will also just run via docker on baremetal

shouldn't matter as long as you're able to authenticate and capture the creds successfully

one issue might have been me provisioning to few resources, I got some failed API calls and unresponsive server, apparently spotizerr crashes before kubernetes can allocate the additional resources, I've now set it to request 1GB RAM and 1.5CPUs, that seems like overkill since it only uses 405m CPUs and ~450MB RAM, but whatever, and now it seems to work way better.

Could have been contributing to your issue, but no need for change if it's working for you now

General Estimates based on variable usage:

Category	Area	Notes / Recommendations
CPU	Concurrency / Downloads	If doing multiple conversions/transcoding (ffmpeg), frequent concurrent downloads for large lists, or writing multiple files, you may want more than 2cpu and above
RAM	Worker Settings	You may want to change your utility worker and librespot concurrency settings in Spotizerr > Config/Settings > Server
RAM	Memory Usage	With API server, multiple workers, and Redis, etc you can probably max out a 1GB RAM allocation, but YMMV.

Recommendations depending on usage: 2 cores & 4gb ram or above

as far as im aware, downloads only work with premium accounts now after spotify api updates. but if flac works, that's good to know and hope that sticks

you might be able to signup with a new account for the new spotify promotion for 4months free only valid til then end of 2025
https://www.spotify.com/us/premium

thanks, may introduce some new updates at some point but all props to the original devs. just keeping the project maintained for now

hey @schoenfbe thanks for the update good to hear it's working for you now. hard to tell but generally looked like a rate limiting issue - might be good to stop/restart your containers, hold back on downloads for a day, and try with the proposed real time/concurrency settings to see if that helps > update: I've managed to install (well, that wasn't the issue) and access spotify on my homelab and have a gui via rdp despite it being headless, so I can try to re-authenticate, and this time it'd indeed be the same physical machine, except if it makes some difference that spotify is running on baremetal and spotizerr in k3s? spotizerr-auth tho will also just run via docker on baremetal - shouldn't matter as long as you're able to authenticate and capture the creds successfully > one issue might have been me provisioning to few resources, I got some failed API calls and unresponsive server, apparently spotizerr crashes before kubernetes can allocate the additional resources, I've now set it to request 1GB RAM and 1.5CPUs, that seems like overkill since it only uses 405m CPUs and ~450MB RAM, but whatever, and now it seems to work way better. - Could have been contributing to your issue, but no need for change if it's working for you now General Estimates based on variable usage: | Category | Area | Notes / Recommendations | |-----------------|------------------|------------------------------------------------------------------------------------------| | CPU | Concurrency / Downloads | If doing multiple conversions/transcoding (ffmpeg), frequent concurrent downloads for large lists, or writing multiple files, you may want more than 2cpu and above | | RAM | Worker Settings | You may want to change your utility worker and librespot concurrency settings in **Spotizerr > Config/Settings > Server** | | RAM | Memory Usage | With API server, multiple workers, and Redis, etc you can probably max out a **1GB RAM** allocation, but YMMV. | - Recommendations depending on usage: 2 cores & 4gb ram or above as far as im aware, downloads only work with premium accounts now after spotify api updates. but if flac works, that's good to know and hope that sticks - you might be able to signup with a new account for the new spotify promotion for 4months free only valid til then end of 2025 `https://www.spotify.com/us/premium` thanks, may introduce some new updates at some point but all props to the original devs. just keeping the project maintained for now