Wrong external ip

[renezuidhof]

I've been trying to set this up for some time now but I keep running into a problem.

proxy | {"level":"error","ts":1760379314.8375764,"msg":"challenge failed","identifier":"mydomain.duckdns.org","challenge_type":"http-01","problem":{"type":"urn:ietf:params:acme:error:connection","title":"","detail":"32.11.39.226: Fetching http://mydomain.duckdns.org/.well-known/acme-challenge/he0RqbfpDH5SNtFl2UnBA0IxMu3l8C1igZDGxtdJGK8: Timeout during connect (likely firewall problem)","instance":"","subproblems":null},"stacktrace":"github.com/mholt/acmez/v3.(*Client).pollAuthorization\n\tgithub.com/mholt/acmez/v3@v3.1.2/client.go:557\ngithub.com/mholt/acmez/v3.(*Client).solveChallenges\n\tgithub.com/mholt/acmez/v3@v3.1.2/client.go:378\ngithub.com/mholt/acmez/v3.(*Client).ObtainCertificate\n\tgithub.com/mholt/acmez/v3@v3.1.2/client.go:136\ngithub.com/caddyserver/certmagic.(*ACMEIssuer).doIssue\n\tgithub.com/caddyserver/certmagic@v0.24.0/acmeissuer.go:489\ngithub.com/caddyserver/certmagic.(*ACMEIssuer).Issue\n\tgithub.com/caddyserver/certmagic@v0.24.0/acmeissuer.go:382\ngithub.com/caddyserver/caddy/v2/modules/caddytls.(*ACMEIssuer).Issue\n\tgithub.com/caddyserver/caddy/v2@v2.10.2/modules/caddytls/acmeissuer.go:288\ngithub.com/caddyserver/certmagic.(*Config).obtainCert.func2\n\tgithub.com/caddyserver/certmagic@v0.24.0/config.go:626\ngithub.com/caddyserver/certmagic.doWithRetry\n\tgithub.com/caddyserver/certmagic@v0.24.0/async.go:104\ngithub.com/caddyserver/certmagic.(*Config).obtainCert\n\tgithub.com/caddyserver/certmagic@v0.24.0/config.go:700\ngithub.com/caddyserver/certmagic.(*Config).ObtainCertAsync\n\tgithub.com/caddyserver/certmagic@v0.24.0/config.go:505\ngithub.com/caddyserver/certmagic.(*Config).manageOne.func1\n\tgithub.com/caddyserver/certmagic@v0.24.0/config.go:415\ngithub.com/caddyserver/certmagic.(*jobManager).worker\n\tgithub.com/caddyserver/certmagic@v0.24.0/async.go:73"}

I think this happens because the external ip address that is received is not correct:
SUCCESS: [mydomain.duckdns.org]> skipped update because IPv4 address is already set to 32.11.39.226

The ip address mentioned above is received using: 'curl -H "Metadata-Flavor:Google" http://metadata/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip'

Though when I check the external ip-address of my Google Cloud instance it's completely different.

Any ideas why this might be happening?

Things I have done:

1. I made sure the firewall rules are configured as described in the readme.
2. I've tried it again with a completely fresh instance
3. I've tried the use=web method as well. This gives me the same ip-address as the use-cmd method.

Note: I used a random ip-address in the code above for 'illustration' purposes

[dadatuputi]

Is this still an issue? It might be necessary to use ACME DNS rather than ACME TLS: https://caddy.community/t/how-to-use-dns-provider-modules-in-caddy-2/8148

[renezuidhof]

I still have this issue, but it might be just me. I'm not expert on these things..

[propstat]

Hey, you likely applied only the port 443 rule and not the port 80 rule.
Check the firewall.