Ability to set custom port

suspicious_cucumber commented

2025-12-19 03:35:31 +00:00

Hi, thanks for your work on reviving this project!

I think it would be great if there was the ability to set a custom port for spotizerr to run on (I use macvlan docker networking so a simple docker-based port mapping (via bridge) won't work in my case).
I am worried that Spotify may wise up to the fact they could just check any dev accounts that have port 7171 in the callback and run a mass-ban. Giving the ability to set a custom port will help give users the flexibility to run a little bit more stealthily :)

Hi, thanks for your work on reviving this project! I think it would be great if there was the ability to set a custom port for spotizerr to run on (I use macvlan docker networking so a simple docker-based port mapping (via bridge) won't work in my case). I am worried that Spotify may wise up to the fact they could just check any dev accounts that have port 7171 in the callback and run a mass-ban. Giving the ability to set a custom port will help give users the flexibility to run a little bit more stealthily :)

Ghost commented

2025-12-20 19:54:06 +00:00

I upvote this feature. I changed my port via the docker mapping, but having a variable in the .env would be great.
Shouldn't be that hard, could you do a PR ?
Also, it would be nice to rename the librespot-spotizerr device when authenticating, maybe Spotify can also track this.

I upvote this feature. I changed my port via the docker mapping, but having a variable in the .env would be great. Shouldn't be that hard, could you do a PR ? Also, it would be nice to rename the librespot-spotizerr device when authenticating, maybe Spotify can also track this.

spotizerrphoenix commented

2025-12-20 22:07:33 +00:00

Owner

hey!

I think it would be great if there was the ability to set a custom port for spotizerr to run on (I use macvlan docker networking so a simple docker-based port mapping (via bridge) won't work in my case).
I am worried that Spotify may wise up to the fact they could just check any dev accounts that have port 7171 in the callback and run a mass-ban. Giving the ability to set a custom port will help give users the flexibility to run a little bit more stealthily :)

This is something that can be looked into. although, you shouldn't have to set your actual redirect url in your spotify api as librespot is doing the heavy lifting and capturing the creds with no redirect callback. for example: https://localhost:3000

api creds are not strictly necessary and reduce rate limiting when searching and can still work with or without it
- you can create a separate anon dev account strictly for api creds and does not need to be tied to your account

Also, it would be nice to rename the librespot-spotizerr device when authenticating, maybe Spotify can also track this.

had some thoughts on this and can look into possibilities of updating the auth tool
from what i've seen, librespot has been working closely with spotify to keep their repo alive and generally seems to be accepted as long as they stay in line with them (but this is speculation)

hey! > I think it would be great if there was the ability to set a custom port for spotizerr to run on (I use macvlan docker networking so a simple docker-based port mapping (via bridge) won't work in my case). I am worried that Spotify may wise up to the fact they could just check any dev accounts that have port 7171 in the callback and run a mass-ban. Giving the ability to set a custom port will help give users the flexibility to run a little bit more stealthily :) This is something that can be looked into. although, you shouldn't have to set your actual redirect url in your spotify api as librespot is doing the heavy lifting and capturing the creds with no redirect callback. for example: `https://localhost:3000` - api creds are not strictly necessary and reduce rate limiting when searching and can still work with or without it - you can create a separate anon dev account strictly for api creds and does not need to be tied to your account > Also, it would be nice to rename the librespot-spotizerr device when authenticating, maybe Spotify can also track this. - had some thoughts on this and can look into possibilities of updating the auth tool - from what i've seen, librespot has been working closely with spotify to keep their repo alive and generally seems to be accepted as long as they stay in line with them (but this is speculation)

suspicious_cucumber commented

2025-12-21 01:46:48 +00:00

Author

Also, it would be nice to rename the librespot-spotizerr device when authenticating, maybe Spotify can also track this.

I had the same thought and opened an issue on the auth repo at the same at the same time I created this issue (see: spotizerrphoenix/spotizerr-auth-phoenix#3)

Shouldn't be that hard, could you do a PR ?

I don't have the skills for this, unfortunately, so any PR I create would be vibe-coded which is unlikely to meet the standards of many.

you shouldn't have to set your actual redirect url in your spotify api as librespot is doing the heavy lifting and capturing the creds with no redirect callback.

Good to know, thank you!! Setting a custom port would still be a nice feature, though perhaps not as pressing as I first expected :)

> Also, it would be nice to rename the librespot-spotizerr device when authenticating, maybe Spotify can also track this. I had the same thought and opened an issue on the auth repo at the same at the same time I created this issue (see: https://lavaforge.org/spotizerrphoenix/spotizerr-auth-phoenix/issues/3) > Shouldn't be that hard, could you do a PR ? I don't have the skills for this, unfortunately, so any PR I create would be vibe-coded which is unlikely to meet the standards of many. > you shouldn't have to set your actual redirect url in your spotify api as librespot is doing the heavy lifting and capturing the creds with no redirect callback. Good to know, thank you!! Setting a custom port would still be a nice feature, though perhaps not as pressing as I first expected :)

spotizerrphoenix commented

2026-01-25 02:49:29 +00:00

Owner

@Ghost wrote in #21 (comment):

Also, it would be nice to rename the librespot-spotizerr device when authenticating, maybe Spotify can also track this.

added new update to spotizerr-auth-phoenix to customize connect device name:

read release notes: https://lavaforge.org/spotizerrphoenix/spotizerr-phoenix/releases/tag/v4.0.16
also recommend to create a new/separate developer spotify account just for api creds and update that in your spotizerr instance > Config > Server tab (since these can function independently)

@Ghost wrote in https://lavaforge.org/spotizerrphoenix/spotizerr-phoenix/issues/21#issuecomment-953: > Also, it would be nice to rename the librespot-spotizerr device when authenticating, maybe Spotify can also track this. added new update to spotizerr-auth-phoenix to customize connect device name: - read release notes: https://lavaforge.org/spotizerrphoenix/spotizerr-phoenix/releases/tag/v4.0.16 - also recommend to create a new/separate developer spotify account just for api creds and update that in your spotizerr instance > Config > Server tab (since these can function independently)

❤️ 1

spotizerrphoenix commented

2026-01-26 20:39:47 +00:00

Owner

Updates if interested:
previously, the entire flow for spotizerr would pass defaults for device info/name which would use identifiers such as librespot and spotizerr 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

Updates if interested: previously, the entire flow for spotizerr would pass defaults for device info/name which would use identifiers such as librespot and spotizerr 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

🚀 1

Rows
Columns

Ability to set custom port #21