On Sun, Mar 08, 2026 at 20:38:09 +0100, Borden wrote: > Needless to say, it still doesn't work with this change enacted. As a > reminder, apache2/error.log reads: > > [dav:error] [pid Y:tid Y] [client 127.0.0.1:46XXX] Unable to PUT new contents > for /webdav/test-text-file.txt. [500, #0] > [dav:error] [pid Y:tid Y] (30)Read-only file system: [client 127.0.0.1:46XXX] > An error occurred while opening a resource for writing: > /var/www/html/webdav/test-text-file.txt. [500, #0]
Assuming you didn't actually mount this file system read-only, my first two guesses for where this additional restriction is coming from would be "systemd unit configuration" or "AppArmor configuration". Check the systemd unit and the /etc/apparmor.d/ directory for anything that might be causing the web server to run with directory restrictions.
