From 241ce960460fbd1356f8d004d6f37964bdd293a0 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 15 Apr 2026 16:31:09 +0000 Subject: [PATCH] fix: remove invalid `servers { name edge }` Caddyfile directive MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `name` is not a valid subdirective of the global `servers` block in Caddyfile syntax — Caddy would reject the config on startup. The dynamic server discovery in `_discover_server_name()` already handles routing to the correct server regardless of its auto-generated name. Co-Authored-By: Claude Opus 4.6 (1M context) --- tools/edge-control/install.sh | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/tools/edge-control/install.sh b/tools/edge-control/install.sh index 4453a5a..fcd33b9 100755 --- a/tools/edge-control/install.sh +++ b/tools/edge-control/install.sh @@ -225,9 +225,9 @@ EOF chmod 600 "$GANDI_ENV" # Create Caddyfile with admin API and wildcard cert -# The "servers" global option names the auto-generated server "edge" so that -# lib/caddy.sh (which discovers the server dynamically) finds a predictable -# name — defense-in-depth alongside the dynamic discovery in add_route. +# Note: Caddy auto-generates server names (srv0, srv1, …). lib/caddy.sh +# discovers the server name dynamically via _discover_server_name() so we +# don't need to name the server here. CADDYFILE="/etc/caddy/Caddyfile" cat > "$CADDYFILE" <<'CADDYEOF' # Caddy configuration for edge control plane @@ -235,9 +235,6 @@ cat > "$CADDYFILE" <<'CADDYEOF' { admin localhost:2019 - servers { - name edge - } } # Default site (reverse proxy for edge tunnels will be added dynamically)