Yesterday, 10:01 PM
(This post was last modified: Yesterday, 10:02 PM by TheDreadPirate. Edited 1 time in total.)
"localhost" only works from the same machine running Jellyfin.
If you did publish port 8096 for the Jellyfin container, you would need to adjust NPM to proxy the host's LAN IP on port 8096 instead of the docker container IP. If NPM is using host networking, you could use "localhost".
THEN you'd be able to go directly to port http://192.168.x.x:8096 on your local clients. And you don't need to put anything in the published URI field.
Publish port 7359 (sounds like you already did)
Publish port 8096
Adjust NPM to proxy the local host IP.
If you did publish port 8096 for the Jellyfin container, you would need to adjust NPM to proxy the host's LAN IP on port 8096 instead of the docker container IP. If NPM is using host networking, you could use "localhost".
THEN you'd be able to go directly to port http://192.168.x.x:8096 on your local clients. And you don't need to put anything in the published URI field.
Publish port 7359 (sounds like you already did)
Publish port 8096
Adjust NPM to proxy the local host IP.
Jellyfin 10.10.3 (Docker)
Ubuntu 24.04 LTS
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)
![[Image: GitHub%20Sponsors-grey?logo=github]](https://img.shields.io/badge/GitHub%20Sponsors-grey?logo=github)
Ubuntu 24.04 LTS
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)