Baikal: Not receiving anything with Thunderbird + Lightning !

[superkrup]

Hi !

I have trouble getting my calendar with Thunderbird + Lightning. What is weird is when I look at the nginx logs, I see the PROPFIND request and it seems that there is no errors :

"PROPFIND /dav.myserver.org/html/cal.php/calendars/username/default/ HTTP/1.1" 200 31 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 Lightning/3.3.2"

I really need some help here… Do you have some ideas ?

[hermann-san]

Hi, I guess you need to provide some more info. Like, what have you done so far? Which URL are you using to connect? Any error messages in Thunderbird? Is there anything between Thunderbird and Baikal that potentially blocks traffic or port (Firewall, etc.). Can you get to the Baikal Dashboard?

[superkrup]

Hi hermann-san ! I am sorry my message wasn't enough detailed.

I don't know if Thunderbird keeps logs that can give me more informations but for now, the only thing I see is the little warning triangle with the following message : "the calendar x is momentarily not available".

As far as I know, there is nothing between Thunderbird and Baikal likely to blocks traffic…

And regarding the Baikal dashboard, I am perfectly able to get the Baikal Dashboard and see the users, the calendars, etc.

I am not sure if these informations will help but I think I don't have much.

[hermann-san]

so you have a different client than Thunderbird and are able to connect with Baikal and sync is ok?
I also have Thunderbird (on Linux) and my sync works fine. This is the URL I'm using in Thunderbird: https://servername.de/baikal-flat/cal.php/calendars/username/calender-name
It's important to get the URL right. Even if you make the tinyiest mistake, it won't work.
Can you please confirm whether or not the connection to Baikal works ok with another client (in the case you've tried it)?

[superkrup]

Nope, I only use thunderbird and here is a screenshot with the error I told you before (it means « the calendar x is momentarily not available » in french)

Regarding the URL, here is the one I use : http://server.org/dav.server.org/html/cal.php/calendars/username/default

I think it is quite the same as yours, don’t you think ?

[hermann-san]

The first part of the URL doesn't look right to me.
dav.server.org/html
are you sure that the folder in which Baikal is installed is correct? so the above line should be the Baikal install foldername.
no need for http_S_ ?
Well , if you can get to the Baikal web admin interface, then the connection to the server should be ok.
It looks to me as if the devil is in the URL, most likely the install foldername.

[superkrup]

I know the URL is weird but it is because I have a directory named "dav.server.org" in my /var/www/ and in this directory I have all the baikal files… (html/admin, html/cal.php, etc.). In fact, at the beginning, I wanted to have a URL like http://dav.server.com/html/ but it wasn't working.

And I do have the https but it is supposed to work with the classic http.

Do you know if there are somewhere some logs I can look at to solve my issue because I am a bit lost here… :(

[hermann-san]

sorry, I'm not aware of Bailkal log-files. Maybe you have to check for Thunderbird/Lightning logfiles as well. Maybe it's even the Thunderbird folks that can help you in their forum.
"dav.server.org/html" is weird to me because I'm on a shared hoster and there I have the html directory which the root directory is. There I have my Baikal folder. So "html" is not part of my URL.
my folder structure is var/www/virtual/username/htm/Baikal-foldername and I only need the Bailkal-foldername.
Maybe those dots in the Baikal foldername are a problem for Thunderbird/Baikal. I don't know. I guess that's not likely to be true, but if everything else fails it might be a worth a try.

[superkrup]

Honestly, I don't think the issue is related to the URL because it was working very well a few days ago. The only thing I did is to update nginx and php5 and after that, synchronization wasn't working anymore.

Perhaps you know a way of doing a "reset" of Baikal ? (without losing my data of course)

[hermann-san]

maybe a backup and restore
https://github.com/netgusto/Baikal/issues/342

[superkrup]

I enabled logs in Thunderbird for Lightning and here are the messages I get when I am trying to synchronise the calendar :

CalDAV: Status 200 on initial PROPFIND for calendar Calendrier
CalDAV: Authentication scheme for Calendrier is none
CalDAV: Failed to determine resource type forCalendrier
[JavaScript Warning: "There has been an error reading data for calendar: Calendar. However, this error is believed to be minor, so the program will attempt to continue. Error code: DAV_NOT_DAV. Description: The resource at « http://server.org/dav.server.org/html/cal.php/calendars/username/default » is either not a DAV collection or not available"]
[JavaScript Warning: There has been an error reading data for calendar: Calendar. However, this error is believed to be minor, so the program will attempt to continue. Error code: READ_FAILED. Description:]

What do you think about this ?

[hermann-san]

The key message seems to be the following:

Error code: DAV_NOT_DAV. Description: The resource at « http://server.org/dav.server.org/html/cal.php/calendars/username/default » is either not a DAV collection or not available"

I my view, the URL you specified is found to be faulty by Thunderbird.
You may try a Android client with Baikal (or a different calDav client) in order to verify that Baikal is working ok. If you can , then it's not on the Baikal side where you have to troubleshoot.

[evert]

The HTTP 200 response indicates that baikal is not sending back a correct response. Could be a server misconfiguration. What happens if you open that url in a browser?

[tiphergane]

Hello @evert, I have the same issue, and if I type the address on a browser Baikal return me the "Baïkal is running allright." as if I was trying to access without the /admin to the web interface

In NginX log (access.log), I find this line:
192.168.1.1 - - [XX/Jan/2016:XX:12:41 +0100] "GET /favicon.ico HTTP/1.1" 200 277 "http://baikal.raspi.home/cal.php/calendars/tiphergane/default/" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.111 Safari/537.36"

[evert]

Are you using rewriting? If you put this full url in a browser:

http://baikal.raspi.home/cal.php/calendars/tiphergane/default/

And you're getting that message, this might suggest you're rewriting urls.

[evert]

No further responses received. If you're willing to help me debug this further, I'll happily reopen this ticket.

[hermann-san]

meanwhile I've the same problem as the people above. evert, I tried your suggestion and was able to login and got the properties there and that stuff. It looks ok to me.

I figured that the problem could be Thunderbird. The problematic configuration is

• one Thunderbird profile
• one Baikal server
• 2 calendars of 2 different users - with different passwords - added to Thunderbird.
• the first calendar works ok, but the second calendar can't be successfully added.

I tried in on Linux and with a fresh installation on Windows. In both instances it didn't work with error messages in Thunderbird (DAV_NOT_DAV)
If someone would like to try this, all one needs is Thunderbird and Baikal with 2 users who both have different passwords. Then add the calender of both users to Lightning (Thunderbird) and you'll (probably) see that the first calendar can be added, but not the second one ( There is no pop-up asking for Username and password).
The odd thing is that I have another instance of Baikal on my shared web hoster with the same user name and password. When add this calender to Thunderbird, then it works right away. TB is not asking for user name and password. This leads me to believe that TB is simply taking the username and password from the first calender (because both baikal server are on the same domain).
So this looks like a TB bug to me, but it would be nice if someone could actually confirm the behaviour with the 2 different user on the same baikal server.

[evert]

Makes sense @hermann-san , that's a known problem. Thunderbird cannot remember more than 1 username/password for a domain.

Your only real option here is to create multiple subdomains that all point to baikal, and use a different subdomain for each user.

[mitar]

It does support more than 1 username/password, but you have to set calendar.network.multirealm setting in Thunderbird to true.