Jellyfin Forum
Clients can discover server but can't connect to it - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+---- Forum: Networking & Access (https://forum.jellyfin.org/f-networking-access)
+---- Thread: Clients can discover server but can't connect to it (/t-clients-can-discover-server-but-can-t-connect-to-it)

Clients can discover server but can't connect to it - OrkaXL - 2025-02-08

The background information:
The problem:
I'm planning on using Jellyfin server locally within my own network using various clients. All of the clients that have an auto-discovery function can discover the server and identify it as http://192.168.x.x:8096 and the same of the server. All of the clients immediately spit out an error message when trying to connect to it: "Tried 2 candidates without success, couldn't reach server." This problem exist on all types of clients (android, windows, TV, etc.).

Network settings in Jellyfin:
  • Bind to local network address is set to the local ip of the server which is static.
  • Allow remote connection box is checked on.
  • Ipv6 is disabled
  • All of the other setting have been left untouched.

Please do let me know if this issue has been resolved in the past or if I need to provide more information.

Thanks in advance for the help.

RE: Clients can discover server but can't connect to it - theguymadmax - 2025-02-08

Version 10.10.5 has a bug that sets the autodiscovery address to 127.0.0.1 by default. You'll need to manually input your local IP address instead.

RE: Clients can discover server but can't connect to it - OrkaXL - 2025-02-09

I have indeed heard about this issue but even manually inputting the server's ip address into various clients returns the same error.

RE: Clients can discover server but can't connect to it - TheDreadPirate - 2025-02-10

What firewall app are you using on LMDE? Does that also use UFW?

What is the output of these commands?

Code:
sudo ss -tulpn | grep 8096
sudo ufw status


RE: Clients can discover server but can't connect to it - OrkaXL - 2025-02-11

I use the standard firewall app, I believe it is called Gufw Firewall and it is version 22.04.0. Port 32400 is also open because of Plex. Can you make something out of these outputs?

The first command returns (X used to mask local ip): tcp LISTEN 0 512 192.168.X.X:8096 0.0.0.0:* users: (("jellyfin",pid=3490,fd=466))

The second command returns: Status: active

To Action From
-- ------ ----
32400/tcp ALLOW Anywhere
8096/tcp ALLOW Anywhere
32400/tcp (v6) ALLOW Anywhere (v6)
8096/tcp (v6) ALLOW Anywhere (v6)

32400/tcp ALLOW OUT Anywhere
8096/tcp ALLOW OUT Anywhere
32400/tcp (v6) ALLOW OUT Anywhere (v6)
8096/tcp (v6) ALLOW OUT Anywhere (v6)

RE: Clients can discover server but can't connect to it - TheDreadPirate - 2025-02-12

Your LAN IP is not sensitive. It is not publicly routable.

I'm surprised service discovery works at all. You normally need to open port 7359 for service discovery to work. Gufw is a GUI for the command line tool UFW.

Code:
sudo ufw allow 7359/udp

Regardless, as theguymadmax stated, service discovery is bugged until 10.10.6 is released.

I don't see why you can't connect by manually typing in the server IP. The port is open and Jellyfin is listening. But it looks like you have it configured to bind to a specific address? What happens if you remove that config and have it listen on all addresses?

RE: Clients can discover server but can't connect to it - OrkaXL - 2025-02-12

I have added the firewall rule that allows port 7359. I have removed the bind to local ip address and restarted the server. Still cannot connect any client to the server. The auto-discovery function is now indeed broken (discovers server at 127.0.0.1:8096), manually putting in the local ip return the same error as previously.

sudo ss -tulpn | grep 8096:

tcp LISTEN 0 512 0.0.0.0:8096 0.0.0.0:* users: (("jellyfin",pid=2977,fd=482))


Sudo ufw staus: Status: active

To Action From
-- ------ ----
32400/tcp ALLOW Anywhere
8096/tcp ALLOW Anywhere
7359/udp ALLOW Anywhere
32400/tcp (v6) ALLOW Anywhere (v6)
8096/tcp (v6) ALLOW Anywhere (v6)
7359/udp (v6) ALLOW Anywhere (v6)

32400/tcp ALLOW OUT Anywhere
8096/tcp ALLOW OUT Anywhere
32400/tcp (v6) ALLOW OUT Anywhere (v6)
8096/tcp (v6) ALLOW OUT Anywhere (v6)

RE: Clients can discover server but can't connect to it - TheDreadPirate - 2025-02-12

Can you share your full jellyfin log via privatebin.net?

RE: Clients can discover server but can't connect to it - OrkaXL - 2025-02-13

Sure, I have added all the logs of 4 days. Maybe you will spot something I don't.

https://privatebin.net/?792f7cf4c77ecb9e#BYTxHWa35USaECnZ8qaBL7AYFUGU1ywvkNYZYwF5e5p1

I have sent you the password in pm.

RE: Clients can discover server but can't connect to it - TheDreadPirate - 2025-02-13

Everything looks fine in the log after you removed the interface bind.

Do you know if LMDE enables apparmor or SELinux? Since the connection attempts from your clients doesn't appear to be reaching Jellyfin at all, something is blocking it prior to reaching Jellyfin.