+- 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:
- Manual installation using the repository: https://jellyfin.org/docs/general/installation/linux#manual-installation-on-debian-ubuntu-and-derivatives
- Server runs LMDE 6: Faye
- Server allows port 8096 through firewall
- Only error in the logs: Warning about the webrootpath: The WebRootPath was not found: /var/lib/jellyfin/wwwroot. Static files may be unavailable.
- Client software on the server also discovers the server and can connect to it.
- Plex media server is installed and fully functional on the server.
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.