Your message dated Mon, 28 Jul 2025 14:21:50 -0700
with message-id <[email protected]>
and subject line Issue fixed a while back
has caused the Debian Bug report #1100995,
regarding freedombox: Radicale stopped working after upgrade to radicale
version 3.5.0-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1100995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100995
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: freedombox
Version: 25.5
Severity: important
Affects: radicale
My radicale calendar based on freedombox no longer seem to work. All my
calendar client requests get 401.
Running 'journalctl -f|grep radic' show these:
mars 21 14:58:35 freedombox apache-access[1086]: [redacted]:443
127.0.0.1 - [redacted] [21/Mar/2025:14:58:34 +0100] "OPTIONS
/radicale/[redacted]/633e907c-[redacted]-a82f4cae0347/ HTTP/2.0" 401
329 "-" "Evolution/3.46.4"
mars 21 14:58:36 freedombox apache-access[1086]: [redacted]:443
127.0.0.1 - [redacted] [21/Mar/2025:14:58:35 +0100] "OPTIONS
/radicale/[redacted]/633e907c-[redacted]-a82f4cae0347/ HTTP/2.0" 401
115 "-" "Evolution/3.46.4"
The upgrade to radicale 3.5.0-1 changed /etc/radicale/config, which I
suspect broke the setup:
diff --git a/radicale/config b/radicale/config
index 0db3a1e..449a7a8 100644
--- a/radicale/config
+++ b/radicale/config
@@ -46,6 +46,9 @@ key = /etc/ssl/private/ssl-cert-snakeoil.key
# SSL ciphersuite, secure configuration: DHE:ECDHE:-NULL:-SHA (see also "man
openssl-ciphers")
#ciphersuite = (default)
+# script name to strip from URI if called by reverse proxy
+#script_name = (default taken from HTTP_X_SCRIPT_NAME or SCRIPT_NAME)
+
[encoding]
@@ -59,8 +62,8 @@ key = /etc/ssl/private/ssl-cert-snakeoil.key
[auth]
# Authentication method
-# Value: none | htpasswd | remote_user | http_x_remote_user | dovecot | ldap |
denyall
-type = remote_user
+# Value: none | htpasswd | remote_user | http_x_remote_user | dovecot | ldap |
oauth2 | pam | denyall
+#type = denyall
# Cache logins for until expiration time
#cache_logins = false
@@ -125,6 +128,15 @@ type = remote_user
# Value: tls | starttls | none
#imap_security = tls
+# OAuth2 token endpoint URL
+#oauth2_token_endpoint = <URL>
+
+# PAM service
+#pam_serivce = radicale
+
+# PAM group user should be member of
+#pam_group_membership =
+
# Htpasswd filename
#htpasswd_filename = /etc/radicale/users
Switching back to auth.type=remote_user in the file do not seem to be
enough. I also tried auth.type=http_x_remote_user, but this did not
solve the issue either. It seem to me Apache is the rejecting part, the
http request do not reach radicale, at least radicale -D do not show any
activity.
Any clues to spare to get my calendar server back in action?
--
Happy hacking
Petter Reinholdtsen
--- End Message ---
--- Begin Message ---
Hello,
The problem that was experienced momentarily could not be reproduced.
Also given that we have now merged MR 2641, I believe switch to Radicale
3.5 will go smoothly when performing distribution upgrade to Trixie.
Closing this issue as there is not more we can do.
Many thanks for an early report that will help users to migrate to Trixie.
--
Sunil
OpenPGP_0x36C361440C9BC971.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
