How to access local JF Docker from FireStick?

[4r5hw45twh]

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-acce...2#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.

[TheDreadPirate]

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

[4r5hw45twh]

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 {app we don't discuss -TDP}. Cannot figure this out yet.


Actually, might make that its own post.

[TheDreadPirate]

For desktop versions of most Linux distros, a MAC randomizer is usually enabled to reduce your activity's trackability when browsing the Internet. Server versions will NOT have that enabled. At least not when you are running a headless server.

IIRC, you are using Ubuntu 24.04, right? I'm having a hard time finding current documentation for this.

Let's try this. Run this command and share the output.

Code:

sudo netplan get all

As for "optimizations", for the functionality you need there isn't much else you can do.

Having your own "network" in docker is fine. Docker would make its own with a random set of IPs. Having your own network gives you more control and consistency with docker IPs. And you can create additional networks down the road if you need more isolation for a particular container, or set of containers.

[4r5hw45twh]

Let's try this.  Run this command and share the output.

Code:

sudo netplan get all

Sorry, was at work and just got home.
Here is the output attached:
   

And yes, latest Ubuntu LTS version. I honestly had no idea there was a specific "Server" variant. Is that what you use?
The one I got/use is this first one (LTS) - https://ubuntu.com/download/desktop

[TheDreadPirate]

I do use the server specific variant. Does not come with a desktop UI by default, has various other minor differences. Like having the MAC randomizer disabled by default.

Ok. One difference I see is that mine uses netplan natively vs yours using networkmanager.

Check out /etc/NetworkManager/ and see if there are any conf files that enable MAC ramdomization.

Also, is your server using WIFI or ethernet? The options I am seeing for MAC randomization primary have to do with WIFI.

https://networkmanager.pages.freedesktop....conf.html

[4r5hw45twh]

Ok.  One difference I see is that mine uses netplan natively vs yours using networkmanager.

Check out /etc/NetworkManager/ and see if there are any conf files that enable MAC ramdomization.

Is netplan better or?
And the conf file there says "no" for the random mac address line. So that's good I guess.

And the server is Ethernet.

[TheDreadPirate]

Netplan is different, not better. But it does make it more difficult to guide you since this is a part of Linux I've rarely had to deal with so can't recite configuration steps from heart like I can for other aspects of Linux.

I'd need my own system to mirror yours, but doing so would risk breaking things so that isn't going to happen.

Regardless, it sounds like you've gotten things mostly figured out. Except the VPN thing.

[4r5hw45twh]

Regardless, it sounds like you've gotten things mostly figured out.  Except the VPN thing.

Yep; pretty much! Everything (for now) works exactly how I'd like it to, but I have no idea how to have stuff in Docker not become inaccessible via domain name the moment the VPN turns on and then instantly work again when I click the button to turn it off. 

I had 2 solutions I thought of: bind {app we don't talk about - TDP} to the network adapter, but to do that, the VPN would need to be on anyway and ProtonVPN on Linux only does IP-based split tunneling, not program-based.

Other solution was move {app we don't talk about - TDP} to Docker as well as my VPN and just have the qBitt container on same network as VPN one, but then I'm afraid that'll mess up my entire setup with {app we don't talk about - TDP} Client since {app we don't talk about - TDP} works with {app we don't talk about - TDP}. So I don't know if I could access {app we don't talk about - TDP} from outside Docker to have {app we don't talk about - TDP} still download stuff to my external hard drive.

Besides those 2 solutions, I'm really not sure how else I could make it work to have my domain name not being able to access my Docker programs the moment it turns on.