Yesterday, 12:46 PM
(This post was last modified: Yesterday, 01:11 PM by RemoteUser1138. Edited 1 time in total.)
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.
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.