caddy-dns/cloudflare

Not able to create certs in Windows

jahanarun opened this issue · 1 comments

I want to add dns challenge for multiple sub-domains through dns challenge.
But I can't get it to work with the latest caddy version in Windows

PS C:\caddy> .\caddy.exe version
2021/03/27 12:29:49 WARNING: proto: file "pb.proto" is already registered
A future release will panic on registration conflicts. See:
https://developers.google.com/protocol-buffers/docs/reference/go/faq#namespace-conflict

v2.4.0-beta.1 h1:Ed/tIaN3p6z8M3pEiXWJL/T8JmCqV62FrSJCHKquW/I=

Caddyfile

{
    # Enable Debug mode
	debug

    # Disable admin console
	admin off

    # Default email for tls
    email {email-here}

    # acme_ca https://acme-staging-v02.api.letsencrypt.org/directory
}
(common) {
    tls {
        issuer acme {
            # dir https://acme-staging-v02.api.letsencrypt.org/directory
            dir https://acme-v02.api.letsencrypt.org/directory
            resolvers 1.1.1.1 1.0.0.1
            dns cloudflare {api-token-here}
        }
        alpn http2
    }
    log {
        output stdout
        format console
    }
}

nextcloud.dexome.com  {
    import common
    reverse_proxy https://dex-nextcloud {
        transport http {
            tls_insecure_skip_verify
        }
    }
    log {
        output file log/nextcloud.json
    }
}

movies.dexome.com  {
    import common
    @local_subnets {
        remote_ip 10.100.30.0/24 10.100.20.0/24
    }
    reverse_proxy @local_subnets http://daemon.dexome.com:7878
    log {
        output file log/radarr.json
    }
}

This is the output from caddy
output.txt

P.S. I am able to create certs using win-acme just fine. So, the problem seems to be in the caddy or caddy-dns side.

This issue got fixed in 2.4.0-beta.2

964e47d