1. Caddy version (caddy version):
2.1
2. How I run Caddy:
systemctl start
a. System environment:
centos7
b. Command:
paste command here
c. Service/unit/compose file:
paste full file contents here
d. My complete Caddyfile or JSON config:
:80 {
file_server
root * /usr/share/nginx/html
handle_path /api/* {
reverse_proxy http://localhost:8070
}
}
dcmzyl.decheng.gov.cn {
handle_path /api/* {
reverse_proxy http://localhost:8070
}
}
http://dcmzyl.decheng.gov.cn {
file_server
root * /home/daijun/html
}
3. The problem I’m having:
{“level”:“error”,“ts”:1610515768.7723167,“logger”:“tls.issuance.acme.acme_client”,“msg”:“challenge failed”,“identifier”:“MYDEMOHOST.com”,“challenge_type”:“http-01”,“status_code”:400,“problem_type”:“urn:ietf:params:acme:error:connection”,“error”:“Fetching http://MYDEMOHOST/.well-known/acme-challenge/mhUfohCxKk0zwHHk59rHeYOAOKm8bLN6DuPbUKZU7pI: Timeout during connect (likely firewall problem)”}
4. Error messages and/or full log output:
Jan 13 14:09:46 dcqmzj-jjyl-server0002.novalocal caddy[19335]: {“level”:“warn”,“ts”:1610518186.5960596,“logger”:“http”,“msg”:“user server is listening on same interface as automatic HTTP->HTTPS redirects; user-configured routes might override these redirects”,“server_name”:“srv0”,“interface”:“tcp/:80”}
Jan 13 14:09:46 dcqmzj-jjyl-server0002.novalocal caddy[19335]: {“level”:“info”,“ts”:1610518186.596636,“logger”:“http”,“msg”:“enabling automatic TLS certificate management”,“domains”:[“dcmzyl.decheng.gov.cn”]}
Jan 13 14:09:46 dcqmzj-jjyl-server0002.novalocal caddy[19335]: {“level”:“info”,“ts”:1610518186.596791,“logger”:“tls”,“msg”:“cleaned up storage units”}
Jan 13 14:09:46 dcqmzj-jjyl-server0002.novalocal caddy[19335]: {“level”:“info”,“ts”:1610518186.5968645,“msg”:“autosaved config”,“file”:"/var/lib/caddy/.config/caddy/autosave.json"}
Jan 13 14:09:46 dcqmzj-jjyl-server0002.novalocal caddy[19335]: {“level”:“info”,“ts”:1610518186.5968728,“msg”:“serving initial configuration”}
Jan 13 14:09:46 dcqmzj-jjyl-server0002.novalocal caddy[19335]: {“level”:“info”,“ts”:1610518186.606195,“logger”:“tls.obtain”,“msg”:“acquiring lock”,“identifier”:“dcmzyl.decheng.gov.cn”}
Jan 13 14:09:46 dcqmzj-jjyl-server0002.novalocal caddy[19335]: {“level”:“info”,“ts”:1610518186.6063805,“logger”:“tls.obtain”,“msg”:“lock acquired”,“identifier”:“dcmzyl.decheng.gov.cn”}
Jan 13 14:09:46 dcqmzj-jjyl-server0002.novalocal caddy[19335]: {“level”:“info”,“ts”:1610518186.6069002,“logger”:“tls.issuance.acme”,“msg”:“waiting on internal rate limiter”,“identifiers”:[“dcmzyl.decheng.gov.cn”]}
Jan 13 14:09:46 dcqmzj-jjyl-server0002.novalocal caddy[19335]: {“level”:“info”,“ts”:1610518186.6069105,“logger”:“tls.issuance.acme”,“msg”:“done waiting on internal rate limiter”,“identifiers”:[“dcmzyl.decheng.gov.cn”]}
Jan 13 14:09:48 dcqmzj-jjyl-server0002.novalocal caddy[19335]: {“level”:“error”,“ts”:1610518188.2137086,“logger”:“tls.obtain”,“msg”:“will retry”,“error”:"[dcmzyl.decheng.gov.cn] Obtain: [dcmzyl.decheng.gov.cn] creating new order: request to https://acme-v02.api.letsencrypt.org/acme/new-order failed after 1 attempts: HTTP 429 urn:ietf:params:acme:error:rateLimited - Error creating new order :: too many failed authorizations recently: see Rate Limits - Let's Encrypt (ca=https://acme-v02.api.letsencrypt.org/directory)",“attempt”:1,“retrying_in”:60,“elapsed”:1.607310379,“max_duration”:2592000}
5. What I already tried:
6. Links to relevant resources:
The server behiend firewall, and only 80 and 443 port is open.
And I checked my html directory, there is .no well-known/ directory created.
It means that Let’s Encrypt wasn’t able to connect to your server. If you are in China, that is a likely reason. You could try using ZeroSSL just to see: