Caddy fails after adding new site

Added a new site to Caddy, it fails to load and I don’t understand why.

actual domains were changed to - for privacy

Log/result after restarting Caddy:

Logs begin at Wed 2019-09-04 18:09:44 EDT. --
Sep 05 10:30:40 caddy[6732]: 2019/09/05 10:30:40 [INFO] - No such site at :80 (Remote:, Referer: )
Sep 05 10:33:08 systemd[1]: Stopping Caddy HTTP/2 web server...
Sep 05 10:33:08 systemd[1]: Stopped Caddy HTTP/2 web server.
Sep 05 10:33:08 systemd[1]: Started Caddy HTTP/2 web server.
Sep 05 10:33:08 caddy[6761]: Activating privacy features... 2019/09/05 10:33:08 [INFO][] acme: Obtaining bundled SAN certificate
Sep 05 10:33:09 caddy[6761]: 2019/09/05 10:33:09 [INFO][] Certificate written to disk: /etc/ssl/caddy/acme/
Sep 05 10:33:09 caddy[6761]: 2019/09/05 10:33:09 open /etc/ssl/caddy/acme/ no such file or directory
Sep 05 10:33:09 systemd[1]: caddy.service: main process exited, code=exited, status=1/FAILURE
Sep 05 10:33:09 systemd[1]: Unit caddy.service entered failed state.
Sep 05 10:33:09 systemd[1]: caddy.service failed.

New site added to Caddyfile (without this added Caddy loads fine):

#Seafile {
    proxy /  {
    header / {
        Strict-Transport-Security "max-age=31536000;"


I’m out of ideas, and there isn’t much info to go on for me to look at.

Unfortunately, with the redactions you’ve made, there’s not enough information to help you. :slightly_frowning_face: Please provide the full and complete log output as well as the version of Caddy you’re using. If you’re not using the latest, please upgrade first.

Bah… looks like I was right… it was a seafile oddity…

Testing with some success now will report back