kamal-proxy: TLS doesn't work: no viable challenge type found
I’m hosting an app on GCP using a free domain from DuckDNS. Ports 80 and 443 are open. After successful deploy accessing the server on https:// doesn’t work. The logs contain this:
2024-09-27T03:20:06.170255841Z {"time":"2024-09-27T03:20:06.169664821Z","level":"INFO","msg":"http: TLS handshake error from 1.2.3.4:47452: acme/autocert: unable to satisfy \"https://acme-v02.api.letsencrypt.org/acme/authz-v3/1111111111\" for domain \"mydomain.duckdns.org\": no viable challenge type found"}
Proxy config in deploy.yml
proxy:
ssl: true
app_port: 3000
host: mydomain.duckdns.org,api.mydomain.duckdns.org
healthcheck:
path: /health
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 3
- Comments: 19
I’ve added support for
HTTP-01challenges in v0.7.0. If anyone wants to try it on that version directly, please do. I will get an updated release of Kamal out shortly that uses this version too.Cloudflare’s proxied connections now work out-of-the-box. Set your SSL mode to something like “Full (strict)”, and it should set itself up automatically.
Also, just circling back to this part of the issue:
@a3kov It does work, yes. Prior to that last commit, this is the only challenge type we were using. Could you check that the IP DuckDNS is returning for your instance is definitely the public IP of your server, and that you can connect to it from outside your network?
Got this working in a branch now and it seems like the right solution. Should have something merged for this soon.
@a3kov thanks, it does seem like that’s a separate issue with DuckDNS then. I’ll look into that a bit later (I’m not sure it’s really a Kamal Proxy issue after all, but I’m curious to see where it fails). Thanks for reporting it.
In the meantime, I believe the
http-01support is what was required for the other cases (e.g. Cloudflare), so I’m closing this one. Feel free to open a new issue if you hit anything else!Anyway, I make a PR #29 to let HTTP-01 challenge available.
Having the same issue with a Cloudflare DNS. It was working previously with Traefik though.
Edited: the solution was to temporarily disable Proxy mode for the domain in Cloudflare.