CalDAV/CardDAV client disregards the server port

asked 2017-03-13 12:41:46 +0300

rtr2001 gravatar image

updated 2017-07-19 09:35:09 +0300

jovirkku gravatar image


I am testing a bit the CalDAV/CardDAV behaviour with a Baikal server in my network.

Baikal runs in an Apache VHost on port 81 (http://server.ip.addr:81)

On port 80 there's another vhost, with other things running

Despite CALDav server running on http://server.ip.addr:81, server side logs show me that it is poking in the vhost bound at port 80. That is, disregards the port in the address. Obviously, it fails to retrieve anything usefull.

The CALDav server is reacheable on port 81 and behaves ok (Calendar in Thunderbird on a linux machine synced just fine)

I restarted msyncd with debug enabled ( as suggested by @chris.adams in various places here) - but can't spot anything about the actual address in the logs on jolla.

I could not find any similar report here - anyone else have this problem?

Jolla C running SF

edit retag flag offensive close delete


May you check with sqlite3 that your CalDAV account parameters are properly stored ? The account DB is in .config/libaccounts-glib/accounts.db.

  • So connect to it with : sqlite3 .config/libaccounts-glib/accounts.db.
  • Find your CalDAV account internal id by browsing the Accounts table (select * from Accounts;), first column is id.
  • Fetch setting for this id: select * from Settings where account = 39; (assuming your account id is 39.

Check that the server_address field is correct (one example is '' for instance). If it's correct, well the bug is somewhere else…

Damien Caliste ( 2017-03-13 14:32:27 +0300 )edit