fix: use tls_insecure_skip_verify token (this Caddy build has no tls{} transport sub-block)

Caddy v2.11.4's caddyfile adapter rejects 'tls { insecure_skip_verify }'
inside transport http (unrecognized subdirective '{') and also rejects
the handler-level form. The working form, verified live against PMS with
a throwaway caddy (200 OK), is the bare token:

    reverse_proxy 192.168.0.235:32400 {
        transport http {
            tls_insecure_skip_verify
        }
    }
This commit is contained in:
Frank committed 2026-08-26 02:16:42 -07:00
1 parent aa473aeddb
commit c8d7ed65c6
3 files changed
+5 -9

No files matched your search

+2 -2
View File
@@ -103,8 +103,8 @@ CADDYFILE="$REPO_ROOT/dankclaw/Caddyfile"
|| { echo "$name: missing PMS upstream"; return 1; }
echo "$block" | grep -q 'transport http' \
|| { echo "$name: upstream must use the http transport with TLS"; return 1; }
echo "$block" | grep -q 'insecure_skip_verify' \
|| { echo "$name: TLS upstream must skip PMS self-signed cert verification"; return 1; }
echo "$block" | grep -q 'tls_insecure_skip_verify' \
|| { echo "$name: TLS upstream must set tls_insecure_skip_verify (PMS self-signed cert)"; return 1; }
done
}