> I remember you have apache installed.
Yes, it's me again. My troubleshooting order is figure it out for > 2 hours ->
mailing list -> file bug report.
The fact that nobody can say "run journalctl -u <units> and that'll show what's
malfunctioning" *is* a bug. I just need to figure out whether it's against
apache, wsgi, radicale or even python.
> Perhaps you access radical via apache only and not uwsgi ? (which I think is
> a good way for you)
I use the recommended configuration following
/usr/share/doc/radicale/README.Debian . I remember radicale being very
difficult to set up the first time, and it breaks my heart that I have to do it
again.
I'm not smart enough for exotic customisations or source code reading. So
whatever the documentation suggests is what I've done, which I'll shortly
prove...
> So to check that you don't use uwsgi give us :
> grep -ri uwsgi /etc/apache2/
/etc/apache2/conf-available/radicale-uwsgi.conf:# Apache2 snippet to serve
Radicale CardDAV/CardDAV service via uWSGI
/etc/apache2/conf-available/radicale-uwsgi.conf:# allow overriding which uWSGI
socket to proxy into
/etc/apache2/conf-available/radicale-uwsgi.conf: ProxyPass
unix:/run/uwsgi/app/${_RADICALE_APP}/socket|uwsgi://${_RADICALE_APP} retry=0
/etc/apache2/conf-available/radicale-uwsgi.conf: ProxyPassReverse
unix:/run/uwsgi/app/${_RADICALE_APP}/socket|uwsgi://${_RADICALE_APP}
/etc/apache2/mods-available/proxy_uwsgi.load:LoadModule proxy_uwsgi_module
/usr/lib/apache2/modules/mod_proxy_uwsgi.so
(these are all factory default files)
> And give us your apache configuration for your host as your problem should be
> there.
Since we previously established that the vhost.conf is OK, here's radicale.conf
, which I largely copied from
/usr/share/doc/radicale/examples/apache2-vhost.conf and haven't changed in
months:
```
Define _DOMAIN my-computerDefine _HOST ${_DOMAIN}
Define _RADICALE_PREFIX /radicale
Include conf-available/radicale-uwsgi.conf
# which I copied from .../examples/apache2-vhost.conf
# authenticate against PAM with mod-authnz-external
# reusing LocationMatch resolved in radicale snippet
DefineExternalAuth pwauth pipe /usr/sbin/pwauth
<LocationMatch "${_RADICALE_LOCATION_MATCH}">
AuthType Basic
AuthName "Radicale: Authentication Required"
AuthBasicProvider external
AuthExternal pwauth
AllowOverride None
<RequireAll>
Require valid-user
Require ip 127.0.0.1 fc00::/7
</RequireAll>
</LocationMatch>
# cleanup temporary variables
UnDefine _DOMAIN
UnDefine _HOST
UnDefine _RADICALE_PREFIX
UnDefine _RADICALE_APP
UnDefine _RADICALE_LOCATION_MATCH
```
For further certainty, I *can* connect to http://localhost/radicale . My
browser prompts for my username and password. Once I enter that, I get a 503
error message. The log error messages say that uwsgi isn't starting or running,
and I don't know how to start it manually, since systemd says the service
doesn't exist, and I suspect it's telling the truth.
With gratitude for your help,
