+- 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: Remote access doesn't work, local access does (/t-remote-access-doesn-t-work-local-access-does)
Remote access doesn't work, local access does - RemoteUser1138 - 2025-09-03
As usual, I have a Jellyfin server that clients can access when connected to the same LAN, but not from "outside" (aka remote access).
The extremely frustrating part: Jellyfin remote access worked fine previously. It simply stopped working a few days ago, for no obvious reason. I haven't changed anything in the setup.
The hardware:
--Windows 11 machine hardwired to
--my router (Ubiquiti Dream Router 7)
--Note: direct connection to fiber on my router via SFP. No ISP-mandated "gateway" box involved (though, Jellyfin remote access did work when I used to have one of those).
The software:
--Windows 11 box runs Jellyfin server and hosts media.
--Ubiquiti router runs a VPN server (Wireguard) for remote access. Which works fine for other services, see below.
Observations:
--Looking through the Jellyfin server's logs in its web GUI, I see that the remote clients were considered to have connected and disconnected, even though I never got a sign of this on the client end & was unable to browse or play media. The clients acted like they could not talk to the server.
--again, local access (client connected directly to same LAN as Windows 11 box) works fine.
--Other LAN resources are remotely accessible through the Wireguard VPN, such as:
---a Bittorrent monitoring app that uses http to provide a web interface. This talks to a Bittorrent instance running on the same machine as Jellyfin.
---networked printer's web interface.
Those last 2 things show me that yes, LAN services + devices should be accessible remotely.
I never had to explicitly allow specific ports, protocols etc. on the Windows machine, or otherwise touch its firewall. Same for the router.
Nobody has a clue over on the Ubiquiti forum.
So, why don't my Jellyfin clients have remote access?
RE: Remote access doesn't work, local access does - gizmomelb - 2025-09-04
Are the remote clients trying to connect using http (port 8096) or https (port 8920)?.
What port / connection type do the local clients successfully connect to?
Asking the obvious - is 'allow remote connections' option in JF enabled?
RE: Remote access doesn't work, local access does - RemoteUser1138 - 2025-09-04
In order asked: Yes, no (I can't be bothered to set up a certificate for HTTPS just yet).
When local, same port, on the usual HTTP connection type (e.g. http://<IP_address_of_Jellyfin_host_machine>:8096).
Yes, allow remote connections is enabled.
I completely uninstalled and reinstalled Jellyfin yesterday, and I *think* remote access is again working as intended, based on a quick test over mobile data. Can verify later today.
RE: Remote access doesn't work, local access does - RemoteUser1138 - 2025-09-04
nope, still not working.
RE: Remote access doesn't work, local access does - RemoteUser1138 - 2025-09-05
Anyone? I'm ready to move on to another solution if Jellyfin won't work.
All indications are that the pipe/access method works fine, since I can get to other LAN resources remotely. It appears to be a problem with the Jellyfin server not responding correctly to remote connection requests.
Looking in the "Activity" area of the Jellyfin server dashboard, I do see that the server detects a remote client (phone, for instance) "Connecting" and then later "Disconnecting." I can tell because the remote client IPs are those associated with my router's Wireguard server.
So, at least some traffic from the clients is in fact getting all the way to the Jellyfin server. The problem is that the server never lets the client browse or play media. All I get on the client end is the "Unable to reach server" error screen.