pelican: pin games.nordhammer.it to LAN IP in panel container
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
584e40d466
commit
3e556581f1
1 changed files with 10 additions and 1 deletions
|
|
@ -89,7 +89,16 @@
|
|||
TRUSTED_PROXIES = "172.16.0.0/12,10.0.0.0/8,127.0.0.1/32";
|
||||
TZ = "Europe/Stockholm";
|
||||
};
|
||||
extraOptions = [ "--add-host=host.docker.internal:host-gateway" ];
|
||||
extraOptions = [
|
||||
"--add-host=host.docker.internal:host-gateway"
|
||||
# The panel calls the node over its public FQDN. Without this the
|
||||
# container's DNS answers with the WAN address and the request
|
||||
# hairpins out through the router and back into the same box — which
|
||||
# works, but breaks whenever the WAN link flaps even though both ends
|
||||
# are local. Pin it to the LAN IP; nginx serves a wildcard cert so
|
||||
# SNI still matches.
|
||||
"--add-host=games.nordhammer.it:10.0.0.1"
|
||||
];
|
||||
};
|
||||
|
||||
virtualisation.oci-containers.containers.pelican-wings = {
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue