Hi there. I’m not sure if this is an appropriate spot to post this but I found this community to be a lot more at my alley and it seems to be more of an English speaking community then what I was observing on the OS wiki page I’m not sure if I was on the wrong page or something, but anyways if this is the wrong spot, please point me in the right direction.
I’m trying to figure out how to make the CasaOS Gateway (casaos-gateway) bind to only one specific IP, not all interfaces. By default, it listens on 0.0.0.0:80, but I want it only on 10.10.255.15:80 — which is reserved for system-level services like SSH, DNS, and the Gateway itself.
I’ve also assigned additional static IPs (like .10, .30, etc.) for Docker containers, using a one-to-one IP-to-container setup to avoid port conflicts (like multiple services needing port 80 or 53). Right now, the Gateway UI shows up on all IPs, which breaks that model.
I’m looking for a clean, native way to isolate the CasaOS Gateway web service from my container IPs — rather than falling back on firewall rules or a reverse proxy workaround.
One of the other issues I’m running into is that my nginx reverse proxy container (which handles Let’s Encrypt HTTP challenges) needs access to port 80, but that port is already being taken by the Gateway UI on all interfaces. So I need to have the Gateway bound to only one dedicated IP and then the container IPs will be fully isolated on a 1:1 mapping of container to dedicated IP.
Is there a config file, environment variable, or undocumented flag that controls not just the port binding but also specifically the IP binding? So far I only see -v and -w.
Hope that all made sense. Any help appreciated! Cheers!