How to access local JF Docker from FireStick?

[4r5hw45twh]

I have a Firestick and I used it to access my server from the local IP (http://localhost:Port) when I hosted my JF server on non-Docker Windows.

However, now I use Ubuntu and my JF is in Docker, so on the JF app on the FireStick, it no longer appears as a local discovered network. How do I achieve this?
My current workaround is just access JF through my domain name, but that's silly when the server is right in my home.

[TheDreadPirate]

IIRC, you are using host networking on the container, correct?

In UFW, you need to ensure there are rules to allow ports 1900 and 7359 in addition to 8096. Port 7359 is used for "service discovery", which is what Jellyfin clients listen need to automatically find local Jellyfin servers. Port 1900 is used for DLNA if you care about that.

Code:

sudo ufw allow 1900/udp
sudo ufw allow 7359/udp

[4r5hw45twh]

IIRC, you are using host networking on the container, correct?

Uhhh, maybe? I just installed Ubuntu and then installed Docker. To get JF & Jellyseer properly directing to my domain via NPM, I did remove "network_mode: host" and changed JF & JS to use a network name that I used with NPM, so that they'd all 3 be on the same network to work together. Because if I kept the "network_mode: host" part on JF docker compose file, my domain wouldn't load up JF.

So at the bottom of all 3 (NPM, JF, & JS) docker compose files, I have:

Code:

networks:
   default:
     external: true
     name: networkname

[TheDreadPirate]

If that is the case, you would need to publish ports 7359 and 1900 in the docker compose.

Code:

ports:
  - 1900:1900
  - 7359:7359

I THINK you would also need to change the publish URI field in Dashboard > Networking.

Code:

all=https://jellyfin.domain.tld

[4r5hw45twh]

If that is the case, you would need to publish ports 7359 and 1900 in the docker compose.

Code:

ports:
  - 1900:1900
  - 7359:7359

What is the best way to do things here? Is it proper/Should I even be having those 3 on their own network name, or should I remove the network name I gave and just change all 3 to "network_mode: host"? Assuming that would still allow people/myself access JF outside of my local network via domain name still. I really just want the most basic, simplest setup I can get to still discover local things on my network when they're inside of Docker but also be accessed outside my network via domain name.

Because if I can just make all 3 of my Docker things "network_mode: host" and not even have to mess with ports on the compose files, wouldn't that be the easiest approach? Unless I'm missing something. Currently, I don't have any ports on my compose file at all. And if I go the ports route that you mentioned, should I also add 8096 and 8920 while I'm at it? And port 1900 is for DLNA, right? So I guess I would need to also add "--net=host" to the compose file too?

[TheDreadPirate]

Using the "ports" parameter in docker compose is essentially "host networking" but only for that port. And, no, you don't need to also publish port 8096 or 8920. Just 7359 and 1900. The Publish URI field should direct local clients to your jellyfin domain name, which would go through NPM.

[4r5hw45twh]

I THINK you would also need to change the publish URI field in Dashboard > Networking.

Code:

all=https://jellyfin.domain.tld

Ok, so I published the ports in the compose file but same issue. Still don't see the local JF server showing up on my Firestick, nor my phone. Can still access it via my domain name, though.

I have not done the publish field yet, though. Is this the box (photo below) you are referring to?
If so, do I put the external domain address here? Or the internal one? And if internal, would that be http://localhost:8096, because that address doesn't work on my server PC since it's in Docker (not sure how to access it locally since it's on there).
EDIT: Ok, if I do the external one and just put "external=https://jellyfin.mydomain.com" in the box, I get the same issue.

The Publish URI field should direct local clients to your jellyfin domain name, which would go through NPM.

So I couldn't do both? Basically, trying to connect to JF on devices that are on my home network with the local IP address, since it makes more sense to connect directly than go through a domain when the server is also right in my home, and when not at home, still connect through my domain. But again, I can't use a local URL because that address doesn't work on my server PC since it's in Docker and not the native PC (not sure how to access it locally since it's on there).

[TheDreadPirate]

"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.

[4r5hw45twh]

"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 "localhost" port 8096 instead of the docker container IP.

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 localhost

Yeah, if I do the localhost on my PC, it won't load JF since JF is in Docker (on same machine).
In NPM, my JF proxy host is "http://jellyfin:8096" But that's because NPM is also running in Docker. So wouldn't "localhost" not work in NPM like that since it's in Docker?

[TheDreadPirate]

Is NPM using host or bridge networking?

Regardless, you could use the physical host's IP, 192.168.X.X, in either network mode.