Caddy On-Demand TLS isn't working

1. My Caddy version (caddy -version):

Caddy v1.0.4

2. How I run Caddy:

caddy -ca https://acme-staging-v02.api.letsencrypt.org/directory

a. System environment:

Ubuntu 18 in a new DO droplet, running on root.

d. My complete Caddyfile:

* {
    root ./www
    browse
    log stdout
    errors stdout
    gzip
    tls {
       max_certs 10
    }
}

*.another.com:443 {
    root ./www
    browse
    gzip
    log stdout
    errors stdout
    tls /etc/letsencrypt/live/thridea.com/fullchain.pem /etc/letsencrypt/live/thridea.com/privkey.pem
}

3. The problem I’m having:

The On-Demand TLS isn’t working.

I also see in the docs that I should be prompt to fill some data or agree some stuff the first time I run Caddy and I haven’t received anything like that.

Also to see the logs I had to explicit pass the -log parameter to the caddy command and I shouldn’t need to do that because I specified that on the Caddyfile.

4. Error messages and/or full log output:

2019/11/22 16:44:02 [INFO][cache:0xc000032a00] Started certificate maintenance routine
2019/11/22 16:44:02 [NOTICE] Sending telemetry: we were too early; waiting 23h16m51.631779299s before trying again
2019/11/22 16:44:34 http: TLS handshake error from 179.53.91.106:56822: no certificate available for 'bookme.rocks'
2019/11/22 16:44:34 http: TLS handshake error from 179.53.91.106:44899: no certificate available for 'bookme.rocks'

Resolved on GitHub: https://github.com/caddyserver/caddy/issues/2895#issuecomment-557695169

1 Like