Abiosoft/caddy as docker container restarting itself -

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: 1stlightenergy.com

I ran this command: docker logs (container ID)

It produced this output: 2022/07/13 23:55:47 failed to obtain certificate: acme: error: 429 :: POST :: https://acme-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rateLimited :: Error creating new order :: too many failed authorizations recently: see Failed Validation Limit - Let's Encrypt, url:
exit status 1

My web server is (include version): abiosoft/caddy

The operating system my web server runs on is (include version): CentOS 3.10.0-862.11.6.el7.x86_64

My hosting provider, if applicable, is: unknown

I can login to a root shell on my machine (yes or no, or I don't know): yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): no

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): unknown

Hello,

I am very new to Caddy and Let's Encrypt, so i apologize if I am in the wrong area.

Today I restarted containers running on a Linux server and since then the container abiosoft/caddy keeps restarting itself. I am not completely sure, but due to the containers restarting there are sites that are refusing to connect.

Below is the error message that shows up - which brought me here. If someone could please help it would be greatly appreciated.

2022/07/14 00:18:03 failed to obtain certificate: acme: error: 429 :: POST :: https://acme-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rateLimited :: Error creating new order :: too many failed authorizations recently: see Failed Validation Limit - Let's Encrypt, url:
exit status 1

You're being ratelimtied because too many authorizations have already failed (presumably because you're in a restart loop).

What you'll need to do is look further back in time and find out what the original error was.

How have you got caddy configured? I believe out-of-the-box Caddy automatic HTTPS supports HTTP/ALPN authentication, which works so long as the webserver is exposed to the internet and has the DNS entries for the domain pointed at it. See Caddy's documentation here: Automatic HTTPS — Caddy Documentation especially the list of requirements for "public domain names".

If it's only some sites, have you checked to make sure DNS is pointed at your server properly? Are you hosting a lot of sites on the affected servers?

4 Likes

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