Calendar / CalDav issues

Workspace
, ,
1

Hi,

Type of installation of Workspace:
Docker via docker-compose (Docker-CommunityServer/docker-compose.workspace_enterprise.yml at master · ONLYOFFICE/Docker-CommunityServer · GitHub)

Package versions:
Control panel: 3.5.2.530
Community Server: 12.6.0.1900
Document Server: 8.0.1.1
Mail Server: 1.6.75

Tested with Thunderbird 115.8.1 & Google Chrome 122.0.6261.69

We are testing Onlyoffice as self-hosted replacement of Google Suite and faced an issue with CalDav / Calendar.
Steps:

  1. On the onlyoffice.our_domain.com/Management.aspx?type=1 we changed
    “Custom domain name” in the “DNS Settings” to onlyoffice.our_domain.com.
  2. Go to https://onlyoffice.our_domain.com/addons/calendar/.
  3. Then edit Calendar → Export and Sync → Copied CalDAV URL
  4. Open it in browser, entered my email and password and asked for username and password again.
  5. Checked radicale.log inside onlyoffice-community-server container:

2024-03-13 13:18:01,530 - [7fb163a3b640] INFO: GET response status for ‘/my@email.com@onlyoffice.our_domain.com/6777e65a-b7b4-497b-ba99-ea989b9e8db4’ in 0.876 seconds: 401 Unauthorized
2024-03-13 13:18:11,854 - [7fb163a3b640] INFO: GET request for ‘/my@email.com@onlyoffice.our_domain.com/6777e65a-b7b4-497b-ba99-ea989b9e8db4’ received from ‘XX.XX.XXX.XXX, 172.27.0.1’ (forwarded by 127.0.0.1) using ‘Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36’
2024-03-13 13:18:11,855 - [7fb163a3b640] INFO: Auth token: ‘ASC radicale:20240313131811:opcyZ2KtUmy0LrzyBIneSFBdtFM=’
2024-03-13 13:18:11,855 - [7fb163a3b640] INFO: Remote host: ‘onlyoffice.our_domain.com’
2024-03-13 13:18:11,873 - [7fb163a3b640] ERROR: Error login response: {‘value’: ‘false’, ‘message’: ‘The remote server returned an error: (404) Not Found.’}
2024-03-13 13:18:11,873 - [7fb163a3b640] INFO: Failed login attempt: ‘my@email.com’
2024-03-13 13:18:12,847 - [7fb163a3b640] INFO: GET response status for ‘/my@email.com@onlyoffice.our_domain.com/6777e65a-b7b4-497b-ba99-ea989b9e8db4’ in 0.993 seconds: 401 Unauthorized

Also we tried to disable “Custom domain name”, in that case we were able to connect to the OnlyOffice calendar by CalDav, and got events. But, we were unable to create events in the Thunderbird and then synchronize it with OnlyOffice, radicale.log:

2024-03-13 13:47:12,293 - [7fb16323a640] INFO: REPORT request for ‘/my@email.com@onlyoffice.our_domain.com/6777e65a-b7b4-497b-ba99-ea989b9e8db4/’ with depth ‘1’ received from ‘XX.XX.XXX.XXX, 172.27.0.1’ (forwarded by 127.0.0.1) using ‘Mozilla/5.0 (X11; Linux x86_64; rv:115.0) Gecko/20100101 Thunderbird/115.8.1’
2024-03-13 13:47:12,293 - [7fb16323a640] INFO: Auth token: ‘ASC radicale:20240313134712:XjfQha66tg2UPQeBvfJ9SUKsAyA=’
2024-03-13 13:47:12,293 - [7fb16323a640] INFO: Remote host: ‘onlyoffice.our_domain.com’
2024-03-13 13:47:14,099 - [7fb16323a640] INFO: Successful login: ‘my@email.com’ → ‘my@email.com@onlyoffice.our_domain.com’
2024-03-13 13:47:14,101 - [7fb16323a640] INFO: REPORT response status for ‘/my@email.com@onlyoffice.our_domain.com/6777e65a-b7b4-497b-ba99-ea989b9e8db4/’ with depth ‘1’ in 1.809 seconds: 207 Multi-Status

Hope that data will be enough to begin investigation.

2

Hello @s.hristenko, :wave:

We need some time to review the issue. I will get back to you shortly. Thank you for providing the information.

4

@s.hristenko

I see that you’ve used Workspace Enterprise.
If you have a valid or trial license, I recommend contacting us through our Helpdesk platform.

We’re continuing to work on this issue. As soon as I have any updates or information, I’ll let you know.

5

@s.hristenko

As far as I know, you’ve already reached out to our guys on Zendesk.
You can continue the conversation there. For our community, I’ll leave information here regarding the second issue.

We have reproduced the first issue using the Custom domain name.

Regarding the second issue with Thunderbird.
Could you please provide additional information?

  • Please send us a video demonstrating the problem.
7

Hi.

I got exactly the same issue described by @s.hristenko.

Were you able to fix it already? I’m kinda struggling with it right now.

Regards.

8

Hi @xionjames

Our team is currently working on resolving this issue. We’ll notify you as soon as the version with the fix is released. Thank you for your patience.

9

I have the same problem of the guy above. Are you still working in this issue? When there will be a bug fix version?

11

Thank you for reaching out.

We’ve added a fix for the issue “Login and password not accepted when exporting the calendar with Custom Domain Name (Reverse Proxy) enabled” in version 12.7.

The release is expected within the next ±2 weeks.