Can`t create events in calendar

[PetroGolovnya]

Modoboa: 1.15
installer used: Yes
Webserver: Nginx
OS: Ubuntu 20.04 LTS

Radicale 2.1.11 from ubuntu repo, modoba installer installed 3.x

Steps to reproduce

With a fresh installation done trough the installer, try to create a new event in calendar Calendar1 for a user and take error 500.

ls /srv/radicale/collections/collection-root/mrfadi@air6x.com/
Calendar1 contacts Meetings

Server response with error - https://paste.centos.org/view/d5deae8f
Radicale config - http://dpaste.com//1KDGW78

[tonioo]

@PetroGolovnya The first link has expired...

[PetroGolovnya]

http://paste.org.ru/?f6h6qh

[tonioo]

@PetroGolovnya I see you're using python 3.8. Modoboa has not been officialy tested with this version.

[PetroGolovnya]

Which version of python you recomend?

[tonioo]

Python 3.7 is the most recent version which is known as compatible.

[PetroGolovnya]

ОК. I try swith to 3.7 and make calendar test.

[PetroGolovnya]

Modoboa: 1.15
installer used: Yes
Webserver: Nginx
OS: Ubuntu 18.04

Radicale 2.1.12 in /srv/radicale
and running
tcp 0 0 127.0.0.1:5232 0.0.0.0:* LISTEN 27154/python3

Python 3.6.9
Restart dovecot and i can create calendar, but can`t create event
When i try to add event in calendar http://paste.org.ru/?b8zv56
Radicale config http://paste.ubuntu.com/p/rgpgRyHbQC/

[tonioo]

@PetroGolovnya does you event contains any special characters? Have you tried using only ASCII chars?

[PetroGolovnya]

Links in last message still accessible.
I always use ASCII chars in event name and calendar name.
Event name not contains any special charters, cyrillic \ chinese letters.
For example:

[tonioo]

@PetroGolovnya Sorry for the delay but can you check that you have caldav version 0.6.2 installed in your virtualenv?

[vnen]

I have the same issue, also using Python 3.8.

Not sure if I'm looking at the right place but it looks like caldav version is 0.5.0 here. Is there an easy way to update this (I'm not familiar with Python virtualenv)?

Edit: I think I got to upgrade it correctly to 0.6.2, but still getting a 500 error just saying that "an internal error occurred".

[tonioo]

@vnen Is this issue still happening?

[vnen]

@tonioo yes. I've upgraded Modoboa to 1.17.0 but I still get the same error.

[tonioo]

@vnen Looks like there was a permission issue in the default configuration. I've pushed a fix and I'll release a new version of the plugin soon. Don't forget to update your plugins too.

[vnen]

@tonioo I updated it but it seems the rights file isn't regenerated, so it's still an issue. Is there a way to force it to regenerate? Or should I just do it by hand?

[tonioo]

@vnen You can call the same command using the --force option. (Look at the /etc/cron.d/modoboa file)