Quoting Borden (2026-03-14 00:27:43) > This seems to be broken again. Some update since 11 March 2026 to the evening > of 12 March 2026 has broken > /usr/share/doc/radicale/examples/apache2-vhost.conf . At least, I haven't > been fiddling with any of the config files. > > I know Apache (mostly) works because it lets me connect to > https://localhost/radicale , which I've been using for the last 3.5 years > until it started throwing 503 errors. I know Radicale is (technically) > working because I can run its service and connect to 127.0.0.1:5232. > > Unfortunately, that's not good enough because I cannot log in to the latter > because it's expecting remote_user credentials and any other authentication > scheme fails. > > On the Apache side, every attempt to connect is getting this error message: > No such file or directory: AH02454: uwsgi: attempt to connect to Unix domain > socket /run/uwsgi/app/radicale/socket (radicale:0) failed > > I have python3-radicale & radicale installed, with all their dependencies, > recommendations and suggestions. > > The fault is probably between apache and uwsgi. But since the stock radicale > configuration files and examples aren't working, I wonder whether they need > tweaking... again.
Please don't reuse old bugreports for (potentially) other issues. What you are describing is likely not specific to radicale but instead systemd no longer supporting sysV init scripts. Regardless if you agree with that suspicion of mine, please do file a new bugreport, as it is much easier to join two bugreports than it is to meaningfully distinguish and keep track of multiple issues lumped into one bugreport. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
