On Mo, 2013-09-09 at 13:16 +0200, Patrick Ohly wrote: > On Mo, 2013-07-29 at 21:38 +0200, Maxime Haselbauer wrote: > > Well at the end of the configuration script, it says "code 207" > > That wasn't an error. > > > If I sync-slow it says error 404 > > Can you try again and send me the syncevolution-log.html of the > target-config side (see in your ~/.cache/syncevolution folder) if it > still fails? > > support from owndrive.com told me that they fixed the problem that I > identified on their side, and now SyncEvolution indeed works with > "--print-databases syncURL=https://my.owndrive.com/";. I haven't tried > syncing, but it should work now.
Maxime sent me a log which still showed a 404 error. I set up owndrive.com as part of the nightly testing and the initial testing (involving sycning) succeeded with a few minor issues (incorrect vCard handling on the server side). Maxime, I ended up using "--print-databases syncURL=https://my.owndrive.com"; to find the default databases. That led me to: caldav: Default calendar (https://my.owndrive.com:443/remote.php/caldav/calendars/pohly/defaultcalendar/) <default> carddav: Contacts (https://my.owndrive.com:443/remote.php/carddav/addressbooks/pohly/contacts/) <default> You log showed that you were using https://my.owndrive.com:443/remote.php/carddav/addressbooks/<user>/default I'm not sure where you got that URL from; please use the output from --print-databases instead. In general it is better to use auto-detection, if it works ;-} -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
