Fix server connection problems
Use this article when Phyn cannot add your Jellyfin server, cannot reach a saved server, or shows a server connection error before you can sign in.
Connection problems usually come from the server address, network path, Jellyfin availability, reverse proxy settings, VPN state, or local network permission. The fastest fix is to test the same address outside Phyn, then adjust the address or network until the device can reach Jellyfin reliably.
Start with the browser test: Open the exact Jellyfin server address in a browser on the same device. If the browser cannot reach Jellyfin, Phyn will not be able to reach it either.
Check the server address
Your Jellyfin address should include http:// or https://. It may also include a port.
Common examples:
http://192.168.1.20:8096https://jellyfin.example.com
Check for these common mistakes:
- Missing
http://orhttps://. - Wrong port, especially when using a local HTTP address.
- Extra spaces before or after the URL.
- A reverse-proxy address that works only outside your home network.
- A local IP address that works at home but not on mobile data or another Wi-Fi network.
- A server URL copied from an admin dashboard that is not reachable from this device.
Test local and remote access separately
If you are at home, test the local address your server uses on your home network. If you are away from home, test the external address, VPN address, or reverse-proxy address you normally use in Jellyfin Web.
| Situation | Address to try |
|---|---|
| You are on the same home network as the server | Local IP or local hostname, such as http://192.168.1.20:8096. |
| You are away from home | Public domain, reverse proxy, or VPN address. |
| You use a VPN | The address that works after the VPN is connected. |
| You use a reverse proxy | The public https:// address configured for Jellyfin. |
Do not mix services: A Jellyseerr, Ombi, or dashboard URL is not the same as your Jellyfin server URL. Phyn needs the Jellyfin address for server login.
Check whether Jellyfin is running
If the address looks correct but still fails, confirm that Jellyfin itself is available.
- Open Jellyfin Web from a browser.
- Sign in with the same user if possible.
- Confirm the Jellyfin home page loads.
- Try from the same Wi-Fi, VPN, or mobile connection you are using in Phyn.
If Jellyfin Web is down, restart Jellyfin or ask the server administrator to check the server.
Fix local network discovery issues
Phyn may ask for local network access so it can discover Jellyfin servers and Cast-enabled devices on your local network. If local discovery does not work, you can still type the server address manually.
If you denied local network access earlier, open your device settings and allow local network access for Phyn. On iOS and macOS, this permission can affect whether local devices appear automatically.
Check reverse proxy and HTTPS setups
If Jellyfin is behind a reverse proxy, make sure the public address actually points to Jellyfin and not another service. Also check that:
- HTTPS certificates are valid.
- The proxy forwards Jellyfin traffic correctly.
- WebSocket and long-running connections are allowed if your setup requires them.
- The address works outside your home network when you are not on Wi-Fi.
- The proxy path matches how Jellyfin is configured.
If a reverse proxy works in Jellyfin Web but fails only in Phyn, try the direct local address while on the home network. This helps separate a proxy issue from an app issue.
Server version or setup wizard errors
If Phyn says the server version is too low, update Jellyfin and try again. Phyn expects a modern Jellyfin server API.
If Phyn says the setup wizard is not complete, open Jellyfin Web as an administrator and finish the Jellyfin setup wizard. Phyn cannot use a server that has not completed initial Jellyfin setup.
If the server worked before but stopped
Think about what changed recently:
- The server restarted or moved to another IP address.
- DNS or reverse proxy settings changed.
- A VPN was enabled or disabled.
- Your phone moved from Wi-Fi to mobile data.
- The Jellyfin server updated or stopped running.
- A firewall rule, router rule, or certificate changed.
After fixing the server or network, close and reopen Phyn, then try the server again.
When to contact support
Contact support if the same address works in a browser on the same device but Phyn still cannot connect. Include the platform, whether the address is local or remote, the exact error message, and whether the server works in Jellyfin Web. Do not send private server URLs publicly.