Jellyfin Remote Access Test
Check the actual public TCP path instead of assuming every remote-access problem is a port-forwarding rule.
Jellyfin remote access diagnosis
Verify the TCP path used by Jellyfin or your reverse proxy, then separate local service, forwarding and upstream NAT problems.
The public IP shown here is detected from this browser request. External probes are restricted to that same public IP.
TCP reachability is only one layer
Jellyfin commonly uses TCP 8096 for HTTP, while secure remote deployments may expose a different HTTPS or reverse-proxy port. A successful TCP probe confirms the path. If Jellyfin still fails, inspect the reverse proxy, TLS, application binding and authentication separately.
Pick the Jellyfin port that is actually exposed
Jellyfin documents TCP 8096 as its default HTTP port and TCP 8920 as its default HTTPS port when HTTPS is enabled. A reverse proxy can expose a different public port, so test the public TCP endpoint clients really use.
UDP 7359 is used for client discovery on the local network. This tool performs an external TCP reachability check, so 7359 is not the port to enter here.
CGNAT test · Double NAT test · Remote-access guide
Official reference: Jellyfin networking documentation.