Unexpected issue starting caddy

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. https://crt.sh/?q=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:

oven.greensideproductions.com.au

I ran this command:

sudo service caddy start

It produced this output:

Apr 4 10:32:04 oven-1 systemd-logind: New session 8 of user mark_p_edwards.
Apr 4 10:34:19 oven-1 systemd: Starting Caddy HTTP/2 web server…
Apr 4 10:34:19 oven-1 caddy: Caddyfile is valid
Apr 4 10:34:19 oven-1 systemd: Started Caddy HTTP/2 web server.
Apr 4 10:34:20 oven-1 caddy: Activating privacy features… 2020/04/04 10:34:20 [INFO] [oven.greensideproductions.com.au] acme: Obtaining bundled SAN certificate
Apr 4 10:34:22 oven-1 caddy: 2020/04/04 10:34:22 [INFO] [oven.greensideproductions.com.au] acme: Obtaining bundled SAN certificate
Apr 4 10:34:23 oven-1 caddy: 2020/04/04 10:34:23 [INFO] [oven.greensideproductions.com.au] acme: Obtaining bundled SAN certificate
Apr 4 10:34:24 oven-1 caddy: 2020/04/04 10:34:24 [INFO] [oven.greensideproductions.com.au] acme: Obtaining bundled SAN certificate
Apr 4 10:34:26 oven-1 caddy: 2020/04/04 10:34:26 [INFO] [oven.greensideproductions.com.au] acme: Obtaining bundled SAN certificate
Apr 4 10:34:27 oven-1 caddy: 2020/04/04 10:34:27 [INFO] [oven.greensideproductions.com.au] acme: Obtaining bundled SAN certificate
Apr 4 10:34:29 oven-1 caddy: 2020/04/04 10:34:29 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 https://letsencrypt.org/docs/rate-limits/, url:
Apr 4 10:34:29 oven-1 systemd: caddy.service: main process exited, code=exited, status=1/FAILURE
Apr 4 10:34:29 oven-1 systemd: Unit caddy.service entered failed state.
Apr 4 10:34:29 oven-1 systemd: caddy.service failed.

My web server is (include version):

caddy

The operating system my web server runs on is (include version):

Centos 7

My hosting provider, if applicable, is:

me

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):

nope.

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

This is my first time using caddy - config seems fine, ip is static, DNS set-up.

What version of Caddy do you have?

@mholt any ideas why Caddy ate through the hourly order limit in a few seconds?

Hi @edwar64896

are you sure your config is correct? Checking your domain - https://check-your-website.server-daten.de/?q=oven.greensideproductions.com.au

Host T IP-Address is auth. ∑ Queries ∑ Timeout
oven.greensideproductions.com.au A 35.189.43.128 Ashburn/Virginia/United States (US) - Google LLC Hostname: 128.43.189.35.bc.googleusercontent.com yes 1 0
AAAA yes
www.oven.greensideproductions.com.au Name Error yes 1 0

Runs your Caddy on that ip address 35.189.43.128?

What’s the ip of that server?

it’s not www.oven.greensideproductions.com.au, its just “oven.greensideproductions.com.au”.

IP address is correct 35.189.43.128

latest stable. I literally only just installed it and attempted to fire it up.

I haven’t been able to reproduce it yet, but someone reported a similar issue just recently in our bug tracker: https://github.com/caddyserver/caddy/issues/3251

They were using Caddy 1, but this issue has been fixed in Caddy 2 for some time now.

1 Like

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