Hello thanks for answering,
The variables are set exactly as mentioned, here is the service file used:
~ # cat /etc/systemd/system/caddy.service
Description=Caddy HTTP/2 web server
; User and group the process will run as.
; Letsencrypt-issued certificates will be written to this directory.
; Always set "-root" to something safe in case it gets forgotten in the Caddyfile.
ExecStart=/usr/local/bin/caddy -log stdout -agree=true -conf=/etc/caddy/Caddyfile -root=/var/tmp
ExecReload=/bin/kill -USR1 $MAINPID
; Use graceful shutdown with a reasonable timeout
; Limit the number of file descriptors; see `man systemd.exec` for more limit settings.
; Unmodified caddy is not expected to use more than that.
; Use private /tmp and /var/tmp, which are discarded after caddy stops.
; Use a minimal /dev
; Hide /home, /root, and /run/user. Nobody will steal your SSH-keys.
; Make /usr, /boot, /etc and possibly some more folders read-only.
; … except /etc/ssl/caddy, because we want Letsencrypt-certificates there.
; This merely retains r/w access rights, it does not add any new. Must still be writable on the host!
; The following additional security directives only work with systemd v229 or later.
; They further retrict privileges that can be gained by caddy. Uncomment if you like.
; Note that you may have to add capabilities required by any plugins in use.
Also the directory permissions looks good to me, here they are:
~ # ls -lah /etc/ssl/caddy/
drwxrwx--- 4 caddy caddy 4.0K May 27 17:26 .
drwxr-xr-x 5 root root 4.0K May 27 16:50 ..
drwx------ 4 caddy caddy 4.0K May 27 17:25 acme
drwx------ 2 caddy caddy 4.0K Jun 2 12:14 ocsp
I also always launched Caddy from the root user, using the provided service file. So obviously there is no
.caddy directory in my
/root/ (as forbidden by the permissions set). Did I done something wrong?