Radicale was working fine on my system yesterday, but today won't start. I suspected an update broke something, but I'm not aware of anything being up dated in the past few days that would affect radicale.

The only logs showing an error are /var/log/apache2/error.log:

[proxy:error] [pid 6765:tid 6765] (2)No such file or directory: AH02454: uw sgi: attempt to connect to Unix domain socket /run/uwsgi/app/radicale/socke
t (radicale:0) failed
[:error] [pid 6765:tid 6765] [client ::1:54892] AH10101: failed to make con nection to backend: radicale:0

repeated over and over again. Apache otherwise shows no errors, and the log
s under /var/log/radicale are empty.

Weirdly, I had to start radicale manually, which I've never had to do befor
e. It ran without error.
In desperation, I tried walking through the instructions atÿ/usr/share /doc/radicale/README.Debian , but I hit a hard stop when I ran `sudo servic
e uwsgi start` and got `Failed to start uwsgi.service: Unit uwsgi.service n
ot found.` But I have all the correct packages installed, so I don't know w
hat could be broken.

I don't know how I'm this unlucky. Does anyone know what might have cause t
his problem and how to fix it?

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 2026-03-13, Borden wrote:

In desperation, I tried walking through the instructions
atÿ/usr/share/doc/radicale/README.Debian , but I hit a hard stop whe

n I ran

`sudo service uwsgi start` and got `Failed to start uwsgi.service: Unit uwsgi.service not found.` But I have all the correct packages installed,

so I

don't know what could be broken.

I remember you have apache installed. Perhaps you access radical via
apache only and not uwsgi ? (which I think is a good way for you)

So to check that you don't use uwsgi give us :
grep -ri uwsgi /etc/apache2/

And give us your apache configuration for your host as your problem
should be there.

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

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 wh at's malfunctioning" *is* a bug. I just need to figure out whether it's aga inst 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/READM E.Debian . I remember radicale being very difficult to set up the first tim
e, 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 w hatever the documentation suggests is what I've done, which I'll shortly pr ove...

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 uW
SGI socket to proxy into
/etc/apache2/conf-available/radicale-uwsgi.conf:ÿÿÿÿ?
?ÿÿ ProxyPassÿÿÿÿÿÿÿ unix:/r un/uwsgi/app/${_RADICALE_APP}/socket|uwsgi://${_RADICALE_APP} retry=0 /etc/apache2/conf-available/radicale-uwsgi.conf:ÿÿÿÿ?
?ÿÿ ProxyPassReverse unix:/run/uwsgi/app/${_RADICALE_APP}/socke t|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 shoul

d 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 br owser 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 runn ing, and I don't know how to start it manually, since systemd says the serv
ice doesn't exist, and I suspect it's telling the truth.
With gratitude for your help,

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

On 2026-03-13, Borden wrote:

/etc/apache2/conf-available/radicale-uwsgi.conf:# Apache2 snippet to serv

e 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}/so cket|uwsgi://${_RADICALE_APP}

/etc/apache2/mods-available/proxy_uwsgi.load:LoadModule proxy_uwsgi_modul

e /usr/lib/apache2/modules/mod_proxy_uwsgi.so

So here you don't enable radicale-uwsgi.conf and don't load uwsgi module

Define _DOMAIN my-computerDefine _HOST ${_DOMAIN}
Define _RADICALE_PREFIX /radicale

Include conf-available/radicale-uwsgi.conf

But here you set some parameters with it (ProxyPass, etc). So it fails as
the module is not loaded. You should comment this include and radicale
will be accessed directly via apache.

<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>

I see none of the radicale parameters which should be there.
To help you find them this is my /radicale block
(I have the same auth variables as yours but in an upper block)

<Location "/radicale/">
CacheDisable on
ProxyPass http://localhost:5232/radicale/ retry=0
ProxyPassReverse http://localhost:5232/radicale/
RequestHeader set X-Script-Name /radicale
RequestHeader set X-Forwarded-Port "%{SERVER_PORT}s"
RequestHeader set X-Forwarded-Proto expr=%{REQUEST_SCHEME}
<IfVersion >= 2.4.40>
Proxy100Continue Off
</IfVersion>
RequestHeader set X-Remote-User expr=%{REMOTE_USER}
</Location>

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

Hi,

Radicale was working fine on my system yesterday, but today won't start.

I suspected an update broke something, but I'm not aware of anything being updated in the past few days that would affect radicale.

The only logs showing an error are /var/log/apache2/error.log:

[proxy:error] [pid 6765:tid 6765] (2)No such file or directory: AH02454:

uwsgi: attempt to connect to Unix domain socket /run/uwsgi/app/radicale/soc
ket (radicale:0) failed

[:error] [pid 6765:tid 6765] [client ::1:54892] AH10101: failed to make c

onnection to backend: radicale:0

This is maybe related to https://bugs.debian.org/1130481

Thanks,

Alex

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)

This is maybe related to https://bugs.debian.org/1130481

Thanks,
Alex

Right you are. For further certainty, there's nothing wrong with my config files (for now). Systemd dropped init.d support upon which, apparently, rad icale relies.

--- PyGate Linux v1.5.13
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)