#dev 2026-07-10

2026-07-10 UTC
cotsuka, paultibbetts, grufwub, ax562, barnaby, d1s1nf3ct, bterry and GWG joined the channel
#
WinnerWind
reverse proxy users? I'm using NGINX (not proxy manager) to manage my hosts but the problem is that if one of my hosts is down because of whatever reason, and i try to restart NGINX, it will crash and all my services collectively go down. I'm using docker with DNS management via a shared network bridge
#
WinnerWind
i can't find any solid documentation on assigning static IP addresses for each container in docker, it seems as though the only way is to use its dns handler which returns a domain not found if the IP being asked for is down
#
doesnm
nginx should not crash because of down upstream
#
doesnm
only if you have invalid config
mcepl left the channel
#
doesnm
try `nginx -t`
#
WinnerWind
so for jellyfin the container is named jellyfin and im doing proxy_pass http://jellyfin; (after definining an upstream to jellyfin:8096)
#
WinnerWind
this is what happens if i down a container and restart nginx
#
doesnm
i'm look later (my vpn slot are busy)
d1s1nf3ct joined the channel
#
doesnm
WinnerWind: wow didn't know that it's a thing
cotsuka, GuestZero, WinnerWind and barnaby joined the channel
#
WinnerWind
welp. made the move to caddy and havent had such issues
cotsuka, ZodiacalComet and [pcarrier] joined the channel
#
[pcarrier]
I would expose the ports and move to localhost:8096 so the upstream doesn't need to resolve maybe?
[pcarrier] joined the channel
#
WinnerWind
[pcarrier]: i have many services that run on port 80. docker COULD rewrite that for me but then id need to memorize a looootttt of port configurations. its way easier to do service:8096 instead of host.docker.internal:10234 because 8096 was for whatever reason taken by something else
#
WinnerWind
not to mention host.docker.internal also gives a potential attacker access to ports i dont want exposed to the webserver, including my private fileshare
#
[pcarrier]
WinnerWind: suit yourself. I wouldn't rely on transient hostnames personally.
#
WinnerWind
[pcarrier]: why not? just curious?
#
[pcarrier]
WinnerWind: it's a recipe for unavailability if things get cached too well, performance degradation if they don't cache well enough
#
[pcarrier]
and it causes your issue.
#
WinnerWind
well, the hostnames aren't really transient. each hostname is assigned to a specific compose file, but i see what you mean
#
WinnerWind
you are right that it causes my issue
#
WinnerWind
[pcarrier]: yup, that's the issue
cotsuka, [schmarty], ax562, barnaby, blacklight, [Murray], Saige_Leah, ZodiacalComet, Pixi` and bterry joined the channel