From e3ec3ae93cd4dcbd97bd5f506d4835c14113c0a9 Mon Sep 17 00:00:00 2001 From: ZDDC Date: Sat, 2 May 2026 11:35:09 -0500 Subject: [PATCH] ci: connect verify step to caddy via container name Runner now runs in a quadlet container on caddy-net, so 127.0.0.1 is the runner's own loopback. Reach the Caddy container by name ('caddy') with --connect-to keeping SNI/Host as the public hostname so the right vhost matches. --- .forgejo/workflows/deploy-content.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.forgejo/workflows/deploy-content.yml b/.forgejo/workflows/deploy-content.yml index cffab40..5dacb17 100644 --- a/.forgejo/workflows/deploy-content.yml +++ b/.forgejo/workflows/deploy-content.yml @@ -30,5 +30,7 @@ jobs: - name: Verify run: | - curl -ksI --resolve zddc.varasys.io:8443:127.0.0.1 \ + # Runner is in a container on caddy-net; reach Caddy by container + # name. See deploy-release.yml in ZDDC for the same pattern. + curl -ksI --connect-to "zddc.varasys.io:8443:caddy:8443" \ https://zddc.varasys.io:8443/ | head -3