Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Cannot get certificate #10

@isZYKerman

Description

@isZYKerman

I tried xcaddy build --with github.com/caddy-dns/tencentcloud --with github.com/mholt/caddy-l4 --with github.com/mholt/caddy-webdav and copied the binary to /usr/bin/. Then I applied the following Caddyfile:

{
        order webdav before file_server
}

*.zykerman.site {
        tls {
                dns tencentcloud {
                        secret_id **********
                        secret_key **********
                }
        }

        @nextcloud {
                host nextcloud.zykerman.site
        }
        handle @nextcloud {
                reverse_proxy localhost:3000
        }

        @jellyfin {
                host jellyfin.zykerman.site
        }
        handle @jellyfin {
                reverse_proxy localhost:8096
        }
}

:8080 {
        #       tls off

        @nextcloud host nextcloud.zykerman.site
        handle @nextcloud {
                reverse_proxy localhost:3000
        }

        @jellyfin host jellyfin.zykerman.site
        handle @jellyfin {
                reverse_proxy localhost:8096
        }
}

But it canNOT get the certificate:

● caddy.service - Caddy
     Loaded: loaded (/usr/lib/systemd/system/caddy.service; enabled; preset: enabled)
    Drop-In: /etc/systemd/system/caddy.service.d
             └─override.conf
     Active: active (running) since Wed 2025-02-05 20:20:07 CST; 22min ago
       Docs: https://caddyserver.com/docs/
   Main PID: 352139 (caddy)
      Tasks: 10 (limit: 38313)
     Memory: 10.9M (peak: 12.9M)
        CPU: 240ms
     CGroup: /system.slice/caddy.service
             └─352139 /usr/bin/caddy run --environ --config /etc/caddy/Caddyfile

2月 05 20:30:31 ZYL-ububtu caddy[352139]: {"level":"info","ts":1738758631.8215373,"logger":"tls.obtain","msg":"obtaining certificate","identifier":"*.zykerman.site"}
2月 05 20:30:31 ZYL-ububtu caddy[352139]: {"level":"info","ts":1738758631.821992,"logger":"tls.issuance.acme","msg":"using ACME account","account_id":"https://acme-staging-v02.api.letsencrypt.org/acme/acct/167762823","account_contact":[]}
2月 05 20:30:35 ZYL-ububtu caddy[352139]: {"level":"info","ts":1738758635.32212,"msg":"trying to solve challenge","identifier":"*.zykerman.site","challenge_type":"dns-01","ca":"https://acme-staging-v02.api.letsencrypt.org/directory"}
2月 05 20:30:39 ZYL-ububtu caddy[352139]: {"level":"error","ts":1738758639.0863872,"logger":"tls.obtain","msg":"could not get certificate from issuer","identifier":"*.zykerman.site","issuer":"acme-v02.api.letsencrypt.org-directory","error":"[*.zykerman.site] solving challenges: waiting for solver certmagic.solverWrapper to be ready: checking DNS propagation of \"_acme-challenge.zykerman.site.\" (relative=_acme-challenge zone=zykerman.site. resolvers=[127.0.0.53:53]): looking up authoritative nameservers: could not determine authoritative nameservers (order=https://acme-staging-v02.api.letsencrypt.org/acme/order/167762823/22421871974) (ca=https://acme-staging-v02.api.letsencrypt.org/directory)"}
2月 05 20:30:39 ZYL-ububtu caddy[352139]: {"level":"error","ts":1738758639.0864208,"logger":"tls.obtain","msg":"will retry","error":"[*.zykerman.site] Obtain: [*.zykerman.site] solving challenges: waiting for solver certmagic.solverWrapper to be ready: checking DNS propagation of \"_acme-challenge.zykerman.site.\" (relative=_acme-challenge zone=zykerman.site. resolvers=[127.0.0.53:53]): looking up authoritative nameservers: could not determine authoritative nameservers (order=https://acme-staging-v02.api.letsencrypt.org/acme/order/167762823/22421871974) (ca=https://acme-staging-v02.api.letsencrypt.org/directory)","attempt":5,"retrying_in":600,"elapsed":631.410531366,"max_duration":2592000}
2月 05 20:40:39 ZYL-ububtu caddy[352139]: {"level":"info","ts":1738759239.0866294,"logger":"tls.obtain","msg":"obtaining certificate","identifier":"*.zykerman.site"}
2月 05 20:40:39 ZYL-ububtu caddy[352139]: {"level":"info","ts":1738759239.0874207,"logger":"tls.issuance.acme","msg":"using ACME account","account_id":"https://acme-staging-v02.api.letsencrypt.org/acme/acct/167762823","account_contact":[]}
2月 05 20:40:41 ZYL-ububtu caddy[352139]: {"level":"info","ts":1738759241.1551611,"msg":"trying to solve challenge","identifier":"*.zykerman.site","challenge_type":"dns-01","ca":"https://acme-staging-v02.api.letsencrypt.org/directory"}
2月 05 20:40:45 ZYL-ububtu caddy[352139]: {"level":"error","ts":1738759245.3617537,"logger":"tls.obtain","msg":"could not get certificate from issuer","identifier":"*.zykerman.site","issuer":"acme-v02.api.letsencrypt.org-directory","error":"[*.zykerman.site] solving challenges: waiting for solver certmagic.solverWrapper to be ready: checking DNS propagation of \"_acme-challenge.zykerman.site.\" (relative=_acme-challenge zone=zykerman.site. resolvers=[127.0.0.53:53]): looking up authoritative nameservers: could not determine authoritative nameservers (order=https://acme-staging-v02.api.letsencrypt.org/acme/order/167762823/22422018284) (ca=https://acme-staging-v02.api.letsencrypt.org/directory)"}
2月 05 20:40:45 ZYL-ububtu caddy[352139]: {"level":"error","ts":1738759245.361792,"logger":"tls.obtain","msg":"will retry","error":"[*.zykerman.site] Obtain: [*.zykerman.site] solving challenges: waiting for solver certmagic.solverWrapper to be ready: checking DNS propagation of \"_acme-challenge.zykerman.site.\" (relative=_acme-challenge zone=zykerman.site. resolvers=[127.0.0.53:53]): looking up authoritative nameservers: could not determine authoritative nameservers (order=https://acme-staging-v02.api.letsencrypt.org/acme/order/167762823/22422018284) (ca=https://acme-staging-v02.api.letsencrypt.org/directory)","attempt":6,"retrying_in":600,"elapsed":1237.685902512,"max_duration":2592000}
~
(END)

I went to see the Dnspod control panel and it seemed that no acme challenge related records was added. Any ideas?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions