Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- [jelly@server:~]$ sudo caddy run (04-01 18:51)
- 2022/04/02 01:51:04.313 INFO using adjacent Caddyfile
- 2022/04/02 01:51:04.316 WARN input is not formatted with 'caddy fmt' {"adapter": "caddyfile", "file": "Caddyfile", "line": 3}
- 2022/04/02 01:51:04.322 INFO admin admin endpoint started {"address": "tcp/localhost:2019", "enforce_origin": false, "origins": ["localhost:2019", "[::1]:2019", "127.0.0.1:2019"]}
- 2022/04/02 01:51:04.322 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/02 01:51:04.322 INFO http enabling automatic HTTP->HTTPS redirects {"server_name": "srv0"}
- 2022/04/02 01:51:04.323 INFO tls.cache.maintenance started background certificate maintenance {"cache": "0xc0004b4000"}
- 2022/04/02 01:51:04.323 INFO tls cleaning storage unit {"description": "FileStorage:/root/.local/share/caddy"}
- 2022/04/02 01:51:04.323 INFO http enabling automatic TLS certificate management {"domains": ["cracken.duckdns.org"]}
- 2022/04/02 01:51:04.323 INFO tls finished cleaning storage units
- 2022/04/02 01:51:04.324 INFO autosaved config (load with --resume flag) {"file": "/root/.local/share/caddy/autosave.json"}
- 2022/04/02 01:51:04.324 INFO serving initial configuration
- 2022/04/02 01:51:04.324 INFO tls.obtain acquiring lock {"identifier": "cracken.duckdns.org"}
- 2022/04/02 01:51:04.442 INFO tls.obtain lock acquired {"identifier": "cracken.duckdns.org"}
- 2022/04/02 01:51:04.865 INFO tls.issuance.acme waiting on internal rate limiter {"identifiers": ["cracken.duckdns.org"], "ca": "https://acme-v02.api.letsencrypt.org/directory", "account": "email@email.com(notactual-input -dimitri)"}
- 2022/04/02 01:51:04.865 INFO tls.issuance.acme done waiting on internal rate limiter {"identifiers": ["cracken.duckdns.org"], "ca": "https://acme-v02.api.letsencrypt.org/directory", "account": "email@email.com(notactual-input -dimitri)"}
- 2022/04/02 01:51:05.353 INFO tls.issuance.acme.acme_client trying to solve challenge {"identifier": "cracken.duckdns.org", "challenge_type": "http-01", "ca": "https://acme-v02.api.letsencrypt.org/directory"}
- 2022/04/02 01:51:05.761 ERROR tls.issuance.acme.acme_client challenge failed {"identifier": "cracken.duckdns.org", "challenge_type": "http-01", "problem": {"type": "urn:ietf:params:acme:error:connection", "title": "", "detail": "Fetching http://cracken.duckdns.org/.well-known/acme-challenge/Bb6pckps1bT1NpPP1NJ77eaqVDCGQ0cvG_R9nIF9GuU: Connection refused", "instance": "", "subproblems": []}}
- 2022/04/02 01:51:05.762 ERROR tls.issuance.acme.acme_client validating authorization {"identifier": "cracken.duckdns.org", "problem": {"type": "urn:ietf:params:acme:error:connection", "title": "", "detail": "Fetching http://cracken.duckdns.org/.well-known/acme-challenge/Bb6pckps1bT1NpPP1NJ77eaqVDCGQ0cvG_R9nIF9GuU: Connection refused", "instance": "", "subproblems": []}, "order": "https://acme-v02.api.letsencrypt.org/acme/order/478919790/76562987000", "attempt": 1, "max_attempts": 3}
- 2022/04/02 01:51:07.200 INFO tls.issuance.acme.acme_client trying to solve challenge {"identifier": "cracken.duckdns.org", "challenge_type": "tls-alpn-01", "ca": "https://acme-v02.api.letsencrypt.org/directory"}
- 2022/04/02 01:51:07.608 ERROR tls.issuance.acme.acme_client challenge failed {"identifier": "cracken.duckdns.org", "challenge_type": "tls-alpn-01", "problem": {"type": "urn:ietf:params:acme:error:connection", "title": "", "detail": "Connection refused", "instance": "", "subproblems": []}}
- 2022/04/02 01:51:07.608 ERROR tls.issuance.acme.acme_client validating authorization {"identifier": "cracken.duckdns.org", "problem": {"type": "urn:ietf:params:acme:error:connection", "title": "", "detail": "Connection refused", "instance": "", "subproblems": []}, "order": "https://acme-v02.api.letsencrypt.org/acme/order/478919790/76562991930", "attempt": 2, "max_attempts": 3}
- 2022/04/02 01:51:09.057 ERROR tls.obtain could not get certificate from issuer {"identifier": "cracken.duckdns.org", "issuer": "acme-v02.api.letsencrypt.org-directory", "error": "[cracken.duckdns.org] solving challenges: cracken.duckdns.org: no solvers available for remaining challenges (configured=[tls-alpn-01 http-01] offered=[http-01 dns-01 tls-alpn-01] remaining=[dns-01]) (order=https://acme-v02.api.letsencrypt.org/acme/order/478919790/76562996560) (ca=https://acme-v02.api.letsencrypt.org/directory)"}
- 2022/04/02 01:51:09.646 INFO tls.issuance.zerossl generated EAB credentials {"key_id": "vdqKyguoCX7-TWxfle2OXA"}
- ^C2022/04/02 01:51:10.239 INFO shutting down {"signal": "SIGINT"}
- 2022/04/02 01:51:10.239 WARN exiting; byeee!! 👋 {"signal": "SIGINT"}
- 2022/04/02 01:51:10.242 INFO tls.cache.maintenance stopped background certificate maintenance {"cache": "0xc0004b4000"}
- 2022/04/02 01:51:10.242 WARN tls.issuance.acme.acme_client HTTP request failed; retrying {"url": "https://acme.zerossl.com/v2/DV90", "error": "performing request: Get \"https://acme.zerossl.com/v2/DV90\": context canceled"}
- 2022/04/02 01:51:10.243 ERROR tls.obtain could not get certificate from issuer {"identifier": "cracken.duckdns.org", "issuer": "acme.zerossl.com-v2-DV90", "error": "provisioning client: context canceled"}
- 2022/04/02 01:51:10.243 INFO tls.obtain releasing lock {"identifier": "cracken.duckdns.org"}
- 2022/04/02 01:51:10.243 ERROR tls.obtain unable to unlock {"identifier": "cracken.duckdns.org", "lock_key": "issue_cert_cracken.duckdns.org", "error": "remove /root/.local/share/caddy/locks/issue_cert_cracken.duckdns.org.lock: no such file or directory"}
- 2022/04/02 01:51:10.244 ERROR tls job failed {"error": "cracken.duckdns.org: obtaining certificate: [cracken.duckdns.org] Obtain: provisioning client: context canceled"}
- 2022/04/02 01:51:10.244 INFO admin stopped previous server {"address": "tcp/localhost:2019"}
- 2022/04/02 01:51:10.244 INFO shutdown complete {"signal": "SIGINT", "exit_code": 0}
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement