1. Caddy version (caddy version
):
v2.4.6 h1:HGkGICFGvyrodcqOOclHKfvJC0qTU7vny/7FhYp9hNw=
2. How I run Caddy:
centos 7
a. System environment:
b. Command:
Paste command here.
c. Service/unit/compose file:
Paste full file contents here.
Make sure backticks stay on their own lines,
and the post looks nice in the preview pane.
d. My complete Caddyfile or JSON config:
02lc.cn {
tls service@daehub.com
respond "Hello, 2world!"
}
localhost {
tls service@daehub.com
respond "Hello, world!"
}
3. The problem I’m having:
4. Error messages and/or full log output:
[root@iZadbuhxtr6g13Z ~]# caddy run --config Caddyfile
2022/04/13 05:26:35.370 INFO using provided configuration {“config_file”: “Caddyfile”, “config_adapter”: “”}
2022/04/13 05:26:35.371 WARN input is not formatted with ‘caddy fmt’ {“adapter”: “caddyfile”, “file”: “Caddyfile”, “line”: 2}
2022/04/13 05:26:35.372 INFO admin admin endpoint started {“address”: “tcp/localhost:2019”, “enforce_origin”: false, “origins”: [“localhost:2019”, “[::1]:2019”, “127.0.0.1:2019”]}
2022/04/13 05:26:35.373 INFO http server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS {“server_name”: “srv0”, “https_port”: 443}
2022/04/13 05:26:35.373 INFO tls.cache.maintenance started background certificate maintenance {“cache”: “0xc000370070”}
2022/04/13 05:26:35.373 INFO http enabling automatic HTTP->HTTPS redirects {“server_name”: “srv0”}
2022/04/13 05:26:35.374 INFO http enabling automatic TLS certificate management {“domains”: [“localhost”, “02lc.cn”]}
2022/04/13 05:26:35.374 INFO autosaved config (load with --resume flag) {“file”: “/root/.config/caddy/autosave.json”}
2022/04/13 05:26:35.374 INFO serving initial configuration
2022/04/13 05:26:35.375 INFO tls.obtain acquiring lock {“identifier”: “localhost”}
2022/04/13 05:26:35.375 INFO tls cleaning storage unit {“description”: “FileStorage:/root/.local/share/caddy”}
2022/04/13 05:26:35.376 INFO tls.obtain acquiring lock {“identifier”: “02lc.cn”}
2022/04/13 05:26:35.379 INFO tls.obtain lock acquired {“identifier”: “localhost”}
2022/04/13 05:26:35.380 INFO tls.obtain lock acquired {“identifier”: “02lc.cn”}
2022/04/13 05:26:35.381 INFO tls finished cleaning storage units
2022/04/13 05:26:35.387 ERROR tls.obtain will retry {“error”: “[localhost] Obtain: subject does not qualify for a public certificate: localhost”, “attempt”: 1, “retrying_in”: 60, “elapsed”: 0.008604828, “max_duration”: 2592000}
2022/04/13 05:26:35.387 INFO tls.issuance.acme waiting on internal rate limiter {“identifiers”: [“02lc.cn”], “ca”: “https://acme-v02.api.letsencrypt.org/directory”, “account”: “service@daehub.com”}
2022/04/13 05:26:35.387 INFO tls.issuance.acme done waiting on internal rate limiter {“identifiers”: [“02lc.cn”], “ca”: “https://acme-v02.api.letsencrypt.org/directory”, “account”: “service@daehub.com”}
2022/04/13 05:26:36.988 ERROR tls.obtain could not get certificate from issuer {“identifier”: “02lc.cn”, “issuer”: “acme-v02.api.letsencrypt.org-directory”, “error”: “HTTP 429 urn:ietf:params:acme:error:rateLimited - Error creating new order :: too many failed authorizations recently: see Rate Limits - Let's Encrypt”}
2022/04/13 05:26:36.988 INFO tls.issuance.acme waiting on internal rate limiter {“identifiers”: [“02lc.cn”], “ca”: “https://acme.zerossl.com/v2/DV90”, “account”: “service@daehub.com”}
2022/04/13 05:26:36.988 INFO tls.issuance.acme done waiting on internal rate limiter {“identifiers”: [“02lc.cn”], “ca”: “https://acme.zerossl.com/v2/DV90”, “account”: “service@daehub.com”}
2022/04/13 05:26:48.081 ERROR tls.obtain could not get certificate from issuer {“identifier”: “02lc.cn”, “issuer”: “acme.zerossl.com-v2-DV90”, “error”: “[02lc.cn] creating new order: fetching new nonce from server: HTTP 500: (ca=https://acme.zerossl.com/v2/DV90)”}
2022/04/13 05:26:48.081 ERROR tls.obtain will retry {“error”: “[02lc.cn] Obtain: [02lc.cn] creating new order: fetching new nonce from server: HTTP 500: (ca=https://acme.zerossl.com/v2/DV90)”, “attempt”: 1, “retrying_in”: 60, “elapsed”: 12.701612127, “max_duration”: 2592000}