docs(deploy): trust the reverse proxy's own fixed address, never a Docker subnet
The compose comments, the releases README and the Unraid template told users to list the Docker network's subnet (172.17.0.0/16 on Unraid) in TITANO_TRUSTED_PROXIES. That range holds the gateway, from which Docker relays IPv6 clients and the host's own connections to published ports, and on the default bridge every other container: each could again pick its X-Forwarded-For and X-Forwarded-Proto. The guidance now names the proxy container's fixed address on a shared user-defined network, warns against subnets, the gateway and the default bridge, and sends a proxy on the Docker host to network_mode: host (loopback). The server's parse error no longer suggests a /12 network. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
This commit is contained in:
4 files changed
+17
-8
No files matched your search
@@ -234,7 +234,7 @@ public sealed class ServerOptions
|
||||
}
|
||||
catch (FormatException ex)
|
||||
{
|
||||
throw new InvalidOperationException($"TITANO_TRUSTED_PROXIES must list IP addresses or networks such as 172.16.0.0/12: {ex.Message}", ex);
|
||||
throw new InvalidOperationException($"TITANO_TRUSTED_PROXIES must list IP addresses (such as 172.30.0.10) or networks in CIDR form: {ex.Message}", ex);
|
||||
}
|
||||
if (ChunkSizeBytes is < 64 * 1024 or > 64 * 1024 * 1024)
|
||||
throw new InvalidOperationException("The chunk size must be between 64 KiB and 64 MiB.");
|
||||
|
||||
Reference in new issue
Block a user