spotizerr/spotizerr
13
30
Fork 6
Code Issues 14 Pull requests 1 Projects Releases Packages 1 Wiki Activity Actions

Reborn from the ashes - Spotizerr-Phoenix #19

New issue
Open
opened 2025-11-25 01:34:20 +00:00 by spotizerrphoenix · 9 comments
spotizerrphoenix commented 2025-11-25 01:34:20 +00:00
Copy link

Would hate to see a great project like this go down in flames, so I'm deciding to maintain it (not a part of the original devs but huge props to them)

after weeks of spotizerr no longer working without the project maintained, i've taken the liberty to create new updated working repos of the spotizerr repos with ci/cd flows to act as the new "maintained" version of spotizerr, now named spotizerr-phoenix

tldr:
Update your docker image from cooldockerizer93/spotizerr to the new image: spotizerrphoenix/spotizerr

  • after updating to the latest image, you "may" need to reauthenticate with the new changes in the new auth tool docker image (spotizerrphoenix/spotizerr-auth )
    • if you are getting login5 errors, follow the steps below:
    • if needed, make a backup of your data directory first which contain your previous creds, config, history, etc
    • delete your old spotify login under Your Spotizerr Instance > Settings > Accounts > [Delete]
    • then run the auth tool like before using docker with the new auth image/repo: docker run --network=host --rm -it spotizerrphoenix/spotizerr-auth
    • make sure you're opening the spotify desktop app on the same machine where the auth tool is running
    • reference: spotizerrphoenix/spotizerr-auth-phoenix#1

latest release notes: https://lavaforge.org/spotizerrphoenix/spotizerr-phoenix/releases/tag/v4.0.13

under spotizerr-phoenix lavaforge account:

and of course huge appreciation for the original devs on spotizerr. if at any point the original spotizerr devs decide to come back, i will be deprecating spotizerr-phoenix. as of now i've decided to maintain spotizerr-phoenix officially.

  • for now these repos will be mainly for upkeep to keep spotizerr-phoenix in a working state but feel free to submit prs for any bugfixes, changes, features!

to all the selfhosters

Would hate to see a great project like this go down in flames, so I'm deciding to maintain it (not a part of the original devs but huge props to them) after weeks of spotizerr no longer working without the project maintained, i've taken the liberty to create new updated working repos of the spotizerr repos with ci/cd flows to act as the new "maintained" version of `spotizerr`, now named `spotizerr-phoenix` **tldr:** Update your docker image from cooldockerizer93/spotizerr to the new image: `spotizerrphoenix/spotizerr` - after updating to the latest image, you "may" need to reauthenticate with the new changes in the new auth tool docker image (`spotizerrphoenix/spotizerr-auth `) - if you are getting `login5` errors, follow the steps below: - if needed, make a backup of your `data` directory first which contain your previous creds, config, history, etc - delete your old spotify login under Your Spotizerr Instance > Settings > Accounts > [Delete] - then run the auth tool like before using docker with the new auth image/repo: `docker run --network=host --rm -it spotizerrphoenix/spotizerr-auth` - make sure you're opening the spotify desktop app on the **same machine** where the auth tool is running - reference: https://lavaforge.org/spotizerrphoenix/spotizerr-auth-phoenix/issues/1 latest release notes: https://lavaforge.org/spotizerrphoenix/spotizerr-phoenix/releases/tag/v4.0.13 --- under spotizerr-phoenix lavaforge account: - https://lavaforge.org/spotizerrphoenix (view all repos) - updated docs link: https://spotizerr-phoenix.readthedocs.io/ - updated librespot-spotizerr-phoenix to adapt to new spotify api changes - implemented login5 method - updated python packages depending on it: `deezspot-spotizerr-phoenix`, `spotizerr-auth-phoenix` - updated `spotizerr-phoenix` to use the new `deezspot-spotizerr-phoenix` package --- and of course huge appreciation for the original devs on spotizerr. if at any point the original spotizerr devs decide to come back, i will be deprecating spotizerr-phoenix. as of now i've decided to maintain `spotizerr-phoenix` officially. - for now these repos will be mainly for upkeep to keep spotizerr-phoenix in a working state but feel free to submit prs for any bugfixes, changes, features! to all the selfhosters
spotizerr-phoenix-logo.png
391 KiB
spotizerr-phoenix-logo.png
👍 3 👀 3 ❤️ 4 🎉 5 🚀 6
yeewhothis commented 2025-11-25 01:46:02 +00:00
Copy link

🔥🪶

🔥🪶
❤️ 1
Krunox commented 2025-11-25 08:03:39 +00:00
Copy link

@spotizerrphoenix Awesome, I like the phoenix in the name! The project is not dead; it's alive again 🐦‍🔥

@spotizerrphoenix Awesome, I like the phoenix in the name! The project is not dead; it's alive again 🐦‍🔥
❤️ 1
lonhdoan commented 2025-11-26 10:28:34 +00:00
Copy link

Thank you very much for keeping this project alive. I'll try your repo tonight. Keep it up!! @spotizerrphoenix

Thank you very much for keeping this project alive. I'll try your repo tonight. Keep it up!! @spotizerrphoenix
❤️ 1
spotizerrphoenix commented 2025-11-27 09:59:03 +00:00
Author
Copy link

@yeewhothis @Krunox @lonhdoan 🙏🏻✊🏻

Added notes above for the new updates to fix the spotify auth. Just pushed the new update so you'll need to make sure to pull the latest images:

Update your docker image from cooldockerizer93/spotizerr to the new image: spotizerrphoenix/spotizerr

  • after updating to the latest image you may need to reauthenticate with the new changes in the new auth tool docker image (spotizerrphoenix/spotizerr-auth)
  • before doing so, make sure to delete your old spotify login in your Spotizerr instance under Settings > Accounts > [Delete]
  • then run the auth tool like before using docker: docker run --network=host --rm -it spotizerrphoenix/spotizerr-auth

latest release notes: https://lavaforge.org/spotizerrphoenix/spotizerr-phoenix/releases

@yeewhothis @Krunox @lonhdoan 🙏🏻✊🏻 Added notes above for the new updates to fix the spotify auth. Just pushed the new update so you'll need to make sure to pull the latest images: Update your docker image from cooldockerizer93/spotizerr to the new image: `spotizerrphoenix/spotizerr` - after updating to the latest image you may need to reauthenticate with the new changes in the new auth tool docker image (`spotizerrphoenix/spotizerr-auth`) - before doing so, make sure to delete your old spotify login in your Spotizerr instance under Settings > Accounts > [Delete] - then run the auth tool like before using docker: `docker run --network=host --rm -it spotizerrphoenix/spotizerr-auth` latest release notes: https://lavaforge.org/spotizerrphoenix/spotizerr-phoenix/releases
❤️ 1
Krunox commented 2025-11-28 03:16:03 +00:00
Copy link

@spotizerrphoenix Awesome! Thank you for your hard work 🔥

@spotizerrphoenix Awesome! Thank you for your hard work 🔥
❤️ 1
lonhdoan commented 2025-11-28 10:44:27 +00:00
Copy link

@spotizerrphoenix Hi, I have just changed the image to spotizerrphoenix/spotizerr.
I haven't done this:
@spotizerrphoenix wrote in #19 (comment):

  • before doing so, make sure to delete your old spotify login in your Spotizerr instance under Settings > Accounts > [Delete]

  • then run the auth tool like before using docker: docker run --network=host --rm -it spotizerrphoenix/spotizerr-auth

But I am still able to download tracks. I will do it when something cracks later and let you know. Tysm!

@spotizerrphoenix Hi, I have just changed the image to spotizerrphoenix/spotizerr. I haven't done this: @spotizerrphoenix wrote in https://lavaforge.org/spotizerr/spotizerr/issues/19#issuecomment-787: > * before doing so, make sure to delete your old spotify login in your Spotizerr instance under Settings > Accounts > [Delete] > > * then run the auth tool like before using docker: `docker run --network=host --rm -it spotizerrphoenix/spotizerr-auth` But I am still able to download tracks. I will do it when something cracks later and let you know. Tysm!
🚀 1
spotizerrphoenix commented 2025-12-20 11:54:46 +00:00
Author
Copy link

Just posting this here for visibility

[Important] Update to spotizerrphoenix/spotizerr:latest or spotizerrphoenix/spotizerr:4.0.15 and above
spotizerrphoenix/spotizerr-phoenix#23

Just posting this here for visibility [Important] Update to `spotizerrphoenix/spotizerr:latest` or `spotizerrphoenix/spotizerr:4.0.15` and above https://lavaforge.org/spotizerrphoenix/spotizerr-phoenix/issues/23
spotizerrphoenix commented 2026-01-25 02:16:50 +00:00
Author
Copy link

just made a new update to spotizerr-phoenix and spotizerr-auth-phoenix

just made a new update to spotizerr-phoenix and spotizerr-auth-phoenix - new release of `spotizerr-auth-phoenix` will give you the ability to custom device info/name with preset defaults - includes logging for debugging purposes - full spotizerr-phoenix release notes: https://lavaforge.org/spotizerrphoenix/spotizerr-phoenix/releases
sp-auth.png
362 KiB
sp-connect-test.png
3.6 KiB
sp-auth.png sp-connect-test.png
❤️ 1
spotizerrphoenix commented 2026-01-26 20:13:37 +00:00
Author
Copy link

previously, the entire flow for spotizerr would pass defaults for device info/name which would use identifiers such as librespot and project-related info in names and system info for new download sessions.

latest updates to spotizerr-phoenix, deezspot-spotizerr-phoenix, and spotizerr-auth-phoenix address this by:

  • https://lavaforge.org/spotizerrphoenix/spotizerr-phoenix/releases
  • allows you to set custom device info/types/name with preset defaults
  • stores that custom device from your auth flow in the /data/creds/blobs/{sp_profile_name}/device.json
    • this is then passed/used when creating new sessions for initiating downloads
  • upgrading to latest spotizerr-phoenix will auto backfill your existing sp profiles with custom default device info to automate this for you.
  • if you wish to use custom device info, recommended to delete your existing spotify auth profiles in the UI then re-authenticate with the latest spotizerr-auth-phoenix tool
  • after setting LOG_LEVEL=DEBUG in spotizerr-phoenix you should see logs in the console during downloads

Example Logs:

2026-01-25 12:00:00 [INFO] Search completed successfully for query: '{NAME_OF_SEARCH_QUERY}'
2026-01-25 12:00:01 [INFO] Using Spotify device info for '{SP_PROFILE_NAME}': name=Computer Speakers type=4 id=vZKjlBUe4OubGDfFbftsEe4fp0ofPDJRgMVl9nHb locale=SE
  • this is passed and happens before connecting with spotify
previously, the entire flow for spotizerr would pass defaults for device info/name which would use identifiers such as librespot and project-related info in names and system info for new download sessions. latest updates to spotizerr-phoenix, deezspot-spotizerr-phoenix, and spotizerr-auth-phoenix address this by: - https://lavaforge.org/spotizerrphoenix/spotizerr-phoenix/releases - allows you to set custom device info/types/name with preset defaults - stores that custom device from your auth flow in the /data/creds/blobs/{sp_profile_name}/device.json - this is then passed/used when creating new sessions for initiating downloads - upgrading to latest spotizerr-phoenix will auto backfill your existing sp profiles with custom default device info to automate this for you. - if you wish to use custom device info, recommended to delete your existing spotify auth profiles in the UI then re-authenticate with the latest spotizerr-auth-phoenix tool - after setting LOG_LEVEL=DEBUG in spotizerr-phoenix you should see logs in the console during downloads Example Logs: ```bash 2026-01-25 12:00:00 [INFO] Search completed successfully for query: '{NAME_OF_SEARCH_QUERY}' 2026-01-25 12:00:01 [INFO] Using Spotify device info for '{SP_PROFILE_NAME}': name=Computer Speakers type=4 id=vZKjlBUe4OubGDfFbftsEe4fp0ofPDJRgMVl9nHb locale=SE ``` - this is passed and happens before connecting with spotify
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
dev
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
spotizerr/spotizerr#19
No description provided.