Internal Server Error with Radicale version 3.3.0-1 using Python-radicale-decsync 2.1.0-2 #1607
Replies: 2 comments
-
Please contact author of 3rd party plugin, so far Radicale has no defined stable API for to be called by 3rd party plugin and internal APIs are subject to be changed at any time. In addition such 3rd party plugins are also not in scope for any tests. |
Beta Was this translation helpful? Give feedback.
-
Thanks, I did that and reported the issue here: 39aldo39/Radicale-DecSync#33. The issue indeed seems to be caused by the plugin because the Radicale server is accessible as lang as I uninstall the plugin and rename the config-file. Am I supposed to close this issue here because it is caused by the plugin? |
Beta Was this translation helpful? Give feedback.
-
I use Radicale as localhost with the Python-radicale-decsync plugin to use my Decsync-calendar in Thunderbird. The calendar data gets syncronized from my smartphone with Syncthing. Since the last update of Radicale and Python in Oktober 16 2024, the Radicale server isn't accessible any more. The login page at localhost:5232 is up, but when I try to log in, I receive the message "Error: 500 Internal Server Error". New calendar events don't arrive in Thunderbird, either. I can't tell if this is an error related to Radicale or Python.
According to the log (
journalctl --user --unit radicale.service
), the radicale server starts at system boot:When I try to access the calender via browser or Thunderbird, I receive the following messages in the log:
The issue occurred with the following program versions:
Radicale: 3.3.0-1
Python: 3.12.7-1
Python-radicale-decsync: 2.1.0-2
These are my system specifications:
OS: Garuda Linux x86_64
Kernel: 6.11.4-zen1-1-zen
DE: GNOME 47.1
WM: Mutter (Wayland)
CPU: 11th Gen Intel(R) Core(TM) i5-1135G7 (8) @ 4.20 GHz
GPU: Intel Iris Xe Graphics @ 1.30 GHz [Integrated]
Beta Was this translation helpful? Give feedback.
All reactions