2025-01-21, 10:51 PM
(This post was last modified: 2025-01-22, 05:44 PM by TheDreadPirate. Edited 2 times in total.)
(2025-01-21, 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 {app we don't discuss -TDP}. Cannot figure this out yet.
Actually, might make that its own post.