I can't connect my Jellyfin account server to Soundiiz – Soundiiz Support

JELLYFIN

Invalid credentials rarely means your password is wrong

That one message covers every way the connection can fail, and the address is behind it far more often than the password.

Start with the address, not the password

Your server either answers us or it does not, and when it does not, we cannot tell why: no reply reads exactly like a refused password. So people retype a password they had right all along. Check that the address opens from outside your network first, and only then suspect your credentials.

What the form asks for

To connect your Jellyfin server to Soundiiz, enter your username and password and fill in the URL address with the protocol scheme: "http://" or "https://". So the URL you use on Soundiiz should be, for example: "http://myip:port".

Your Jellyfin username, the one you sign in with on the server itself.

Its password. It is required here, so an account set up without one cannot be connected.

The full address, protocol and port included, as the field itself shows.

Soundiiz runs on its own servers, so an address that only exists on your home network gets us nowhere. If it starts with 192.168, or reads localhost, or ends in .local, it works for you and for nobody outside.

Letting us reach the server

Then, ensure that your Jellyfin network configuration allows remote access and port forwarding if required.

If the address is right and the connection still fails, something along the way is turning us back.

A protection layer such as Cloudflare, treating our requests as bot traffic.

A closed port, or a router that never forwards it.

A server that answers too slowly, so we give up before it replies.

A certificate your browser accepts but nothing else does, on an https address.

Cloudflare is the one with an answer of its own, since switching it off is rarely an option: it needs the Soundiiz addresses let through, and a page of its own shows how to find them in your logs.

Connected, but playlists fail

If you're unable to create a playlist with Soundiiz for Jellyfin (you'll see an error message), ensure you can create a playlist yourself in Jellyfin. For example, if you are using Docker, be sure to map the playlist directory too to your composer script.

We cannot do what Jellyfin will not let you do

Soundiiz acts as you, with your account and your rights. So the test that settles it is to make the playlist by hand on the server: if that fails there, it will fail here, and the fix belongs to your Jellyfin setup.

Frequently Asked Questions

Which address should I put in, exactly?

The one that opens Jellyfin from outside your home, port and all. A good test: open it on your phone with the wifi off. If Jellyfin appears, that address will work here too.

It works in my browser but not on Soundiiz

Your browser is on your network, or holds a session, or trusts a certificate it was told to trust once. We arrive with none of that. Nine times out of ten the address is a local one, and the tenth is a protection layer refusing an unknown visitor.

Do I have to leave the server on?

Yes, both to connect and while a transfer runs. Your music lives on that machine and nowhere else, so a server that sleeps halfway through takes your playlists with it.

Still refused?

Send us the address you entered, with the password removed, and tell us whether it opens from outside your network. That pair points at the cause almost every time.

Contact Support