I have php-fpm installed and running on Arch. I’m running caddy as a systemd service. My DNS is configured and a mediawiki installation is in the root directory. Navigating to my URL Caddy produces:
After hours of fucking around with this, I’ve gotten PHP working if I run caddy -conf="/my/conf/Caddyfile", but when I start it with systemctl start caddy it won’t come up.
This is extremely frustrating, I don’t understand why it just doesn’t work.
I suspect it’s a permissions error causing the start job to fail.
Here is my Caddyfile:
/etc/caddy/Caddyfile
www.701sm.club {
root /var/www/701sm.club
log access.log (this sometimes give a permission error in journalctl)
errors errors.log
fastcgi / unix:/var/run/php-fpm/php-fpm.sock php
}
journalctl says it starts and then immediately dies, so it most be a config issue.
Here is my service:
[Unit]
Description=Caddy HTTP/2 web server
Documentation=https://caddyserver.com/docs
After=network-online.target
Wants=network-online.target systemd-networkd-wait-online.service
[Service]
Restart=on-failure
; User and group the process will run as.
User=www-data
Group=www-data
; Letsencrypt-issued certificates will be written to this directory.
Environment=HOME=/etc/ssl/caddy
; 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
; Limit the number of file descriptors; see `man systemd.exec` for more limit settings.
LimitNOFILE=1048576
; Unmodified caddy is not expected to use more than that.
LimitNPROC=64
; Use private /tmp and /var/tmp, which are discarded after caddy stops.
PrivateTmp=true
; Use a minimal /dev
PrivateDevices=true
; Hide /home, /root, and /run/user. Nobody will steal your SSH-keys.
ProtectHome=true
; Make /usr, /boot, /etc and possibly some more folders read-only.
ProtectSystem=full
; … 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!
ReadWriteDirectories=/etc/ssl/caddy
; 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.
;CapabilityBoundingSet=CAP_NET_BIND_SERVICE
;AmbientCapabilities=CAP_NET_BIND_SERVICE
;NoNewPrivileges=true
[Install]
WantedBy=multi-user.target