Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

Thunderbird Version 78 - CalDav calender not working with error PROPFIND "405 Method Not Allowed".

  • 5 trả lời
  • 1 gặp vấn đề này
  • 1 lượt xem
  • Trả lời mới nhất được viết bởi rde

more options

Since the update to Thunderbird 78 my CalDav calender cannot be activated anymore. It appears grey in the calendar list. I checked on multiple computers and my colleagues have the same problem. Is there a way to fix this?

Since the update to Thunderbird 78 my CalDav calender cannot be activated anymore. It appears grey in the calendar list. I checked on multiple computers and my colleagues have the same problem. Is there a way to fix this?

Được chỉnh sửa bởi Wayne Mery vào

Giải pháp được chọn

It turns out that it was indeed related do the UserAgent being rejected by the CalDav-Server after the update to version 78. In that version Lightning is part of Thunderbird and not shown in the user-agent string.

A workaround would be to manually override the general.useragent.locale string in settings with an old one.

Đọc câu trả lời này trong ngữ cảnh 👍 0

Tất cả các câu trả lời (5)

more options

Hi, It didn't worked for me either and I have switched back to 6.8 version. You should wait till the authors update that add-on or you might switch back to an old version.

more options

The error-message ist PROPFIND "405 Method Not Allowed". Is it possible that it has something to do with the user agent that differes in version 78 from version 68 and therefore the client ist no longer accepted?

more options

Giải pháp được chọn

It turns out that it was indeed related do the UserAgent being rejected by the CalDav-Server after the update to version 78. In that version Lightning is part of Thunderbird and not shown in the user-agent string.

A workaround would be to manually override the general.useragent.locale string in settings with an old one.

more options

actually that's not a solution. but since your topic is marked solved i opened a new topic for the problem: https://support.mozilla.org/en-US/questions/1323344