2025-09-03, 07:05 PM
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?
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?
