home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.16k stars 29.84k forks source link

Caldav: 405 error when attempting to login - Failed to Connect #111432

Closed Joshndroid closed 3 months ago

Joshndroid commented 6 months ago

The problem

I am unable to setup a Baikal CalDav calendar within the integration.

I input all of the required login information and it 'Failed to Connect'.

I tried a few times with 'https' in the URL as well as SSL on/off with no difference.

Checking the home assistant logs I see this;

CalDAV client error: PropfindError at '405 Not Allowed b'<html>\n<head><title>405 Not Allowed</title></head>\n<body>\n<center><h1>405 Not Allowed</h1></center>\n<hr><center>nginx/1.25.3</center>\n</body>\n</html>\n'', reason no reason

I have the calendar working in Davx5, thunderbird, outlook just fine so only real conclusion is that there is something going on with the integration.

I see there is another Baikal related issue (https://github.com/home-assistant/core/issues/111421) however their error code seems to be different to what I am experiencing, hence the new issue

What version of Home Assistant Core has the issue?

core-2024.2.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

CalDav

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 6 months ago

caldav documentation caldav source

tobixen commented 6 months ago

This sounds like a compatibility problem between the python-caldav library and your calendar server. If you are willing to make a test account for me at your server or share some username/password with me (privately) I could probably look into it.

issue-triage-workflows[bot] commented 3 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.