Caddy docker doesn't see my TLS email

Hello, I’m trying to use Caddy as a reverse proxy for ASP.NET Core, which has been working so far. The only problem is that Caddy doesn’t seem to be recognizing my TLS email, giving the following output:

Your sites will be served over HTTPS automatically using Let's Encrypt.
By continuing, you agree to the Let's Encrypt Subscriber Agreement at:
Please enter your email address to signify agreement and to be notified
in case of issues. You can leave it blank, but we don't recommend it.

01/29 19:16:32 registration error: acme: error: 429 :: POST :: :: urn:ietf:params:acme:error:rateLimited :: Error creating new account :: too many registrations for this IP: see, url: 

exit status 1
  Email address: 

This is my Caddyfile:

mydomain.dom {
        proxy / web {

It behaves as if there was no email set in the Caddyfile.

And I know it’s being rate limited, that’s not the issue.

Hi @pipe01,

What’s your caddy -version, how do you run Caddy, and what CLI flags do you set?

Just to check, that’s your entire Caddyfile - there’s no other sites configured?

I’m wondering if this recent bug is relevant:

The version command gives Caddy 0.11.2 (unofficial). I’m running it with a docker-compose file, along with other services. That’s the entire file, I know it’s being read because other changes do apply correctly.

Can you try changing the version to 0.11.1 and checking if the problem persists?

0.11.1 seems to be working, I’ll stick to that until a fix comes up. Thanks!

@pipe01 Please try with and report back ASAP whether the bug is still occurring.

Thank you for that, but how could I try that with docker?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.