2025-09-08, 03:23 AM
(This post was last modified: 2025-09-08, 03:51 AM by RemoteUser1138. Edited 1 time in total.)
Some experiments I've tried in the meantime:
I have two other processes with web GUIs on the mentioned Win11 host, accessible through ports 8080 and 8081. I have no problem connecting to those remotely via Wireguard VPN clients.
To see what would happen, I temporarily assigned port 8081 to Jellyfin (vice the usual 8096 default). Didn't make a difference. Remote clients still couldn't get Jellyfin access.
Seems like the problem has nothing to do with specific ports being blocked by some part of Windows, rather the Jellyfin server does not react correctly to access attempts by remote clients.
I also tried Emby. Same behavior, so IDK wtf is going on.
I have two other processes with web GUIs on the mentioned Win11 host, accessible through ports 8080 and 8081. I have no problem connecting to those remotely via Wireguard VPN clients.
To see what would happen, I temporarily assigned port 8081 to Jellyfin (vice the usual 8096 default). Didn't make a difference. Remote clients still couldn't get Jellyfin access.
Seems like the problem has nothing to do with specific ports being blocked by some part of Windows, rather the Jellyfin server does not react correctly to access attempts by remote clients.
I also tried Emby. Same behavior, so IDK wtf is going on.