HTTP 400 when trying to connect via caldav

Bug
1

Hi, some weeks ago my Caldav connection from tasks.org stopped working, meaning the client couldn’t reach the Vikunja server anymore.

I use vikunja.cloud, it says its version v0.24.1-482-3659b7b58d

I tried it with both Tasks.org and Davx5, both don’t work anymore.

Maybe it’s related to this commit: chore(caldav): refactor fetching projects · d081cf80fc - vikunja - Gitea ?

It fails on the /dav/projects endpoint. I can connect to the server but it seems the projects discovery is broken.

1 Like
2

I’ve been struggling with the same thing. When I first add the Vikunja caldav info to Tasks.org (and Davx5) it works once, but all further synch attempts fail (and the url appears to be changed from “dav/principals/username” to /dav/projects)

I think it has been happening since before the commit you linked…

3

I was able to reproduce it, but it’s a little unclear why it is happening. Will look into a fix, but happy to take pointers.

Can you recall a date when it stopped working?

4

I believe it was in the springtime of this year (the issue was confused by switching phones and other challenges with tasks.org)

5

This should now be fixed in 5abca0927b, please check with the next unstable build (should be ready for deployment in ~45min, also on try).

Turns out, when no project was provided (which is intended as the client was fetching the list of all projects), the request would fail because no project was provided.

6

Awesome thank you for the fix. I appreciate that a ton :+1:

Is there any release plan for Vikunja.cloud? On there we still are on Version: v0.24.1-562-c9a68d3a63 (at least that what it says :smiley: )

7

The changes are already on Vikunja Cloud.

The Cloud deployment runs an unstable build, built from the git hash in the version displayed at the end. In the version you provided, that would be c9a68d3a63. The “562” before that means the version has 562 more changes that happened after the 0.24.1 release.

You can check the date of the commit hash in the code repository. We do this to get the latest improvements faster to the hosted version, instead of waiting for a release. Releases contain all fixes that the Cloud hosting already has, the Cloud hosting just usually gets them faster.

You can find more information about the version string in the docs:

1 Like