> The documentation patch I posted above gave me a working installation of > radicale. If you still have permission error, maybe I can help you with some > clue about the owner of radicale data and the systemd configuration used to > run radical (e.g. systemctl cat [email protected]) and maybe an > explicit error message.
Thank you for your help. Before you responded, I got it working, largely thanks to your documentation and freedombox's merge: https://salsa.debian.org/freedombox-team/freedombox/-/merge_requests/2768. I'm definitely, 100%, never going to understand Linux. systemctl daemon-reload and systemctl restart apache2 apparently don't do what I thought they do. Hard reboot applied whatever I did. Consistent with your suggestions, I changed: /etc/apache2/conf-available/radicale-uwsgi.conf 51,52c51,52 - ProxyPass unix:/run/uwsgi/app/${_RADICALE_APP}/socket|uwsgi://${_RADICALE_APP} retry=0 - ProxyPassReverse unix:/run/uwsgi/app/${_RADICALE_APP}/socket|uwsgi://${_RADICALE_APP} + ProxyPass unix:/run/uwsgi/${_RADICALE_APP}.socket|uwsgi://${_RADICALE_APP} retry=0 + ProxyPassReverse unix:/run/uwsgi/${_RADICALE_APP}.socket|uwsgi://${_RADICALE_APP} # create and enable [email protected] & [email protected] $ systemctl edit [email protected] [Service] User=radicale Group=radicale StateDirectory=radicale DynamicUser=no (I look forward to the Internet's feedback about how this is terrible security practice) Linking /var/lib/radicale/collections/collection-root/${USER} to ${HOMEDIR}/${radicale folder}/... works with the same permissions set under init.d . Could we change radicale-uwsgi.conf & make uwsgi-app@radicale.{service, socket} during package installation?
