diff options
| author | Bjørn Forsman <bjorn.forsman@gmail.com> | 2025-12-21 16:02:06 +0100 |
|---|---|---|
| committer | Bjørn Forsman <bjorn.forsman@gmail.com> | 2026-01-16 17:52:21 +0100 |
| commit | c98cf6835b4f1e9aed4bfd0d3ac6143e2cbaaf11 (patch) | |
| tree | 3a3ed4a856f9cbe73d7af80388bd7fccc5238f94 /pkgs/development/python-modules/rangehttpserver | |
| parent | c1aa7496dbca459cd04e8b2248514a04eb2b3053 (diff) | |
nixos/acme: fix ReadWritePaths for acme-${domain}.service
Currently ReadWritePaths is only sufficiently specificed for
acme-order-renew-${domain}.service, and not acme-${domain}.service. This
results in service failure if specifying the webroot outside of
/var/lib/acme, for example /var/www/challenges:
acme-example.com-start[1379]: + mkdir -p /var/www/challenges//.well-known/acme-challenge
acme-example.com-start[1382]: mkdir: cannot create directory ‘/var/www/challenges//.well-known’: Read-only file system
systemd[1]: acme-example.com.service: Main process exited, code=exited, status=1/FAILURE
Fix it by adding the webroots to ReadWritePaths in the common
serviceConfig, where it can affect both acme-order-renew-${domain}.service
AND acme-${domain}.service.
Avoid adding subdirs of existing ReadWritePaths entries, because
otherwise systemd will fail to set up the services, for example:
acme-zeroconf.example.test.service: Failed to set up mount namespacing: /run/acme: No such file or directory
(Confusingly, the path shown in the error message isn't necessarily
related to the problematic path.)
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions
