+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: General Questions (https://forum.jellyfin.org/f-general-questions)
+--- Thread: How to access local JF Docker from FireStick? (/t-how-to-access-local-jf-docker-from-firestick)
Pages:
1
2
RE: How to access local JF Docker from FireStick? - 4r5hw45twh - 2025-01-21
(Yesterday, 10:09 PM)TheDreadPirate Wrote: Is NPM using host or bridge networking?
Regardless, you could use the physical host's IP, 192.168.X.X, in either network mode.
From your above reply:
"If NPM is using host networking, you could use 'localhost'."
I feel like I should take everything that's in Docker (JF, JS, & NPM) and just make them all "--net=host", like I referenced here in the other thread: https://forum.jellyfin.org/t-how-to-access-local-jf-docker-from-firestick?pid=49722#pid49722
I feel like that'd be the best/easiest solution to all my issues maybe. Assuming my setup will still work how it is if I do that.
I assume bridge network for NPM since I never set one up initially, however, I do have it set to be on a network with JF & JS. So those 3 all have the same network section of their docker compose files.
EDIT: Ok, doing the NPM change and adding 8096 to compose file *is* allowing me to now use "localhost:8096" from the native machine. Awesome.
However, I still do not see the server being discovered on my devices as local server.
EDIT2: Ok, so I actually *am* getting access on my FireStick and phone if I use the server's local IP, but it isn't showing on discovered.
I randomly decided to type it in just to test and it actually let me in. So, why wouldn't it show as discovered, though?
Also, is there a better way to achieve this than having the local machine's IP in NPM? Because if the server local IP ever changes, that forces me to have to change the IP on a bunch of stuff now.
RE: How to access local JF Docker from FireStick? - TheDreadPirate - 2025-01-21
You should be setting a static IP for the server. You can do this either by just directly setting an IP on the server or by going into your router and configuring a static assignment for the server.
If you've switched all the containers to host networking, ensure you cleared the Published URI field in Jellyfin. Also make sure that the host firewall is also allowing port 7359 through the firewall.
Code:
sudo ufw allow 7359/udpRE: How to access local JF Docker from FireStick? - 4r5hw45twh - 2025-01-21
(Yesterday, 10:41 PM)TheDreadPirate Wrote: You should be setting a static IP for the server. You can do this either by just directly setting an IP on the server or by going into your router and configuring a static assignment for the server.
If you've switched all the containers to host networking, ensure you cleared the Published URI field in Jellyfin. Also make sure that the host firewall is also allowing port 7359 through the firewall.
Code:sudo ufw allow 7359/udp
Yeah, the static IP is a little weird. I use a router with FreshTomato on it and assigned a static IP to my server's MAC address, but then the MAC address would randomize sometimes between reboots.
Currently, my containers are still using the network name I made up. What would best practice and the simplest route be?
Like, if a professional Linux or Docker or NPM user/dev saw my setup and how it's configured, what could be optimized/changed?
Would they be like, "nah, change those custom network names and just make them all host" or what?
Setup is:
Domain name with Cloudflare pointing to my server's public IP.
Docker has NPM, JF, & JS in it and is managed by NPM.
NPM's proxy host IP for JF is now the server's native local IP instead of "jellyfin".
JF docker compose file now has the ports you mentioned earlier in it, and now 8096 too.
Each docker compose file for each program in Docker ends with the custom network name I gave them.
Regarding VPN, I use ProtonVPN but I only want it On for qBittorrent. Cannot figure this out yet.
Actually, might make that its own post.