Spotify Redirect URI, and other recommendations for Spotify to Navidrome playlist transfers via CLI (Windows)

[candideu]

Hello! Thank you so much for making this incredible tool! I've recently moved my library to Navidrome, and was dreading having to rebuild my playlists manually. This tool is a godsend, and I wanted to share some insights that could help future users (and that may require some changes to the CLI generator):

Spotify Redirect URI

I'm following the Wiki's instructions to get Spotify set up, and when creating the app, it says to do the following:

Add http://localhost:8888/callback as a Redirect URI. Just copy and paste this URL without making any changes.

However, the CLI command (generated using the builder) didn't work... Spotify has made changes this month for newly created apps, and redirect URIs. localhost is not allowed as redirect URI, and they expect "all clients to migrate to the new redirect URI validation by November 2025."

As an alternative, their docs say:

If you are using a loopback address, use the explicit IPv4 or IPv6, like http://127.0.0.1:PORT or http://[::1]:PORT as your redirect URI.

So I had to change it to http://127.0.0.1:8888/callback in both the app and the generated command.

This means that the CLI command builder and Wiki page may need to be updated.

---

CLI Tips

As mentioned, I'm using the CLI generator, and ran into quite a few issues (aside from the one mentioned above).

Here are some tips that could help anyone who's in the same situation as me:

• If using Windows: make sure the command is all in one line, and remove the linebreaks and backticks that the generator provides
• If your navidrome instance is found at an https:// address, your port will be 443 (I didn't know this was a thing, and spent way too much time trying to figure it out)
• add "quotes" around any values with special characters

Here is the command that worked for me (replace highlighted with your own credentials):

tunesynctool --spotify-client-id 12345-client-ID --spotify-client-secret 12345-client-secret --spotify-redirect-uri http://127.0.0.1:8888/callback --subsonic-base-url https://my.navidrome.instance.com --subsonic-port 443 --subsonic-username username --subsonic-password "your-password-would-go-here" transfer --from spotify --to subsonic 12345-spotify-playlist-ID

---

I've shared some step-by-step instructions for beginners here: https://gist.github.com/candideu/29dbbaf7f346d85ede11e465f183b889

[WilliamNT]

Thank you for using tunesynctool, notifying me of the Spotify changes and of course for your thorough documentation! I have updated the builder and the wiki with your recommendations in mind. That being said, there won't be an update to the Python package anytime soon because I am currently occupied with personal things and the upcomming webui aswell.

Regarding the Navidrome issue with SSL, I will investigate it. You say your instance was behind port 443. As far as I know, Navidrome doesn't directly support SSL certificates, so that means you are using a reverse proxy to mask Navidrome. Could you let me know if my assumption is correct?

[candideu]

upcomming webui aswell

A web UI would be lovely!!

Regarding the Navidrome issue with SSL, I will investigate it. You say your instance was behind port 443. As far as I know, Navidrome doesn't directly support SSL certificates, so that means you are using a reverse proxy to mask Navidrome. Could you let me know if my assumption is correct?

Yes, well, a Cloudflare Tunnel. Is that the same thing? I'm still very new to this stuff, and had trouble when I entered the same port number of the instance on my local network, and only foun out about the 443 thing after doing some digging. I guess that's probably obvious to people who are experienced in self-hosting.

[WilliamNT]

Yes, a Cloudflare Tunnel is similar to a reverse proxy, meaning you "mask" the original IP and port of your Navidrome instance by a different hostname (your domain) and well, a different port in most cases. 443 is the standard HTTPS port.