Issue with the errors directive

[p3lim]

If I enable the errors directive as such:

errors {
    log stdout
}

I get the following error:

Activating privacy features…YYYY/MM/DD HH:MM:SS [INFO][errors] acme: Obtaining bundled SAN certificate
YYYY/MM/DD HH:MM:SS [errors] failed to get certificate: acme: Error 400 - urn:acme:error:malformed - DNS name does not have enough labels

If I try to add a custom 404 page as described in the docs I get this:

YYYY/MM/DD HH:MM:SS /etc/caddy/Caddyfile:17 - Parse error: Unknown directive ‘404’

Not sure what’s wrong here.

[matt (Matt Holt)]

What’s your entire Caddyfile?

[p3lim]

errors {
    log stdout
    404 404.html
}

p3lim.net {
    tls redacted@email.tld
    proxy / https://p3lim.github.io {
        transparent
    }
}

*.p3lim.net:80 {
    tls off
    redir https://p3lim.net{uri}
}

It’s the first block that’s giving me errors, running Caddy 0.9.1 on Ubuntu Server 16.04 x64.

It’s running as a service, entirely mirrored the guidelines found here:
https://github.com/mholt/caddy/tree/master/dist/init/linux-systemd

[matt (Matt Holt)]

Ah.

The Caddyfile always starts with the address of the site to serve.

—First line of Caddyfile syntax documentation

Hope that helps!

[p3lim]

Edit: scratch that, moved the errors block to the bottom of the Caddyfile, still getting the same errors.

[matt (Matt Holt)]

Make sure that your Caddyfile is structured properly. Caddy is expecting a site name where you have a directive.

[p3lim]

/facepalm

I’m just so used to nginx where you can have global settings for multiple servers.