-
Notifications
You must be signed in to change notification settings - Fork 313
Description
Checklist
- I have used the search function for OPEN issues to see if someone else has already submitted the same feature request.
- I have also used the search function for CLOSED issues to see if the feature is already implemented and just waiting to be released.
- I will describe the problem with as much detail as possible.
- This is not about the docker image. In that case, contact the authors of the docker image.
Common problems checklist
- I have installed the release zip, not the source code zip
- I have moved the whole, untouched
Specificandconfigfolders to the new installation
Baikal version before
0.9.4 or 0.9.5, can’t recall at the moment
Baikal version after
0.11.1
PHP version
8.4
Problem you are having
TLDR: No calendar clients work with my installation any more.
I was planning to upgrade in-place, but it required php 8.2 (I was running 8.1). Okay, so I tried to upgrade php only to realize my server OS was out of date. After upgrading, it broke everything, so I restored the pre-upgrade snapshot.
After that, I decided to start fresh (I’d been wanting to anyway). Clean start using Caddy as a webserver. Baikal installed correctly, everything is hunky-dory. When trying to connect with any calendar app (to then resync my exported .ics and .vcf files), none of them work with varying levels of verbosity as to why.
The only one to give me any indication is DAVx5. This error (Expected 207 Multi-Status, got 200) DOES show up in the closed issues here on GitHub, but for an older version of Baikal and it did not really help in my situation.
I verified the permissions matched the directories in the known working snapshot. I even at one point purged Caddy and set up Nginx only to have the same issue, even when copying the conf file straight from my backups.
I even rolled back to php 8.2 and no dice.
Which logs or debug dumps would help? Baikal itself, DAVx5, Caddy?