We have moved to a new Sailfish OS Forum. Please start new discussions there.
3

Owncloud 8 Caldav and carddav synchronisation

asked 2015-09-07 02:48:15 +0300

Usegui gravatar image

I have this problem:

If I creat two different accounts

One for caldav with login password and server : http://ip-address/owncloud/remote.php/caldav/calendars/username/personal

the app find 3 calendars: personal username and birthday

Second for carddav: with same login and password and server: http://ip-address/owncloud/remote.php/caldav/calendars/username/personal

The app make the synchronisation for the carddav Everything works find.

But if I creat an account with caldav and carddav then no synchronisation append caldav or carddav. (see the parameters)

login: login

password: **

server: http://ip-address/

caldav: owncloud/remote.php/caldav/calendars/username/personal

carddav: owncloud/remote.php/caldav/calendars/username

What is wrong ?

Thanks

edit retag flag offensive close delete

Comments

i have the same problem with cozy cloud. maybe try as dmnk proposal. i didnt do it but i'll try it too

cemoi71 ( 2015-09-07 10:12:13 +0300 )edit

3 Answers

Sort by » oldest newest most voted
2

answered 2015-09-07 08:03:19 +0300

dmnk gravatar image

with the current versions of OC and SF you can skip the paths for caldav and carddav, as they're found through auto-discovery.

does that change anything?

edit flag offensive delete publish link more

Comments

This is only semi-true because it only works with ownCloud installations in the root directory of the web server. For details see here.

Yo ( 2015-09-07 11:41:16 +0300 )edit

Here a comment I gave earlier in another question regarding auto discovery and well-known-URIs:

RFC 5785 specifies ./well-known-URIs: A well-known URI is a URI whose path component begins with the characters "/.well-known/". So it's forbidden to have something like example.org/owncloud/.well-known/. This is also explained in Appendix B: 4. Why aren't per-directory well-known locations defined? So it's not Jollas fault that auto discovery does not work on ownCloud installations that aren't installed in server root.

Yo ( 2015-09-07 11:47:30 +0300 )edit
1

that's semi true too, as you can place the .well-known folder in the root directory and expand the path with the prefix /owncloud-dir-whatever/ which should create a working state too :)

dmnk ( 2015-09-07 12:09:59 +0300 )edit

@dmnk That's exactly what is proposed in my given link. Didn't read?

Yo ( 2015-09-07 12:33:15 +0300 )edit

i just tried to help with distilled relevant information instead of further readings (no i didn't re-read the thread, cause i already knew it, pretty popular as you might now too ;) )

and you stated that it doesn't work outside of the root directory and gave further readings, which is actually plain wrong.

dmnk ( 2015-09-07 12:46:37 +0300 )edit
1

answered 2015-09-07 11:40:20 +0300

Yo gravatar image

updated 2015-09-07 11:49:53 +0300

There is a detailed answer available that gives advice how to to it. There are 3 possibilities for account setup when using owncloud not in the root directory of the server (which seems to be the case with your installation).

Feel free to update the wiki page.

edit flag offensive delete publish link more
0

answered 2015-09-07 10:39:12 +0300

tonza gravatar image

updated 2015-09-07 10:46:40 +0300

I was able to enable Owncloud contacts and calendars with single account using following,

caldav, /owncloud/remote.php/caldav/calendars/username

carddav, /owncloud/remote.php/carddav/addressbooks/username/contacs

I've since removed the /owncloud/ from URL but when I had it I think it needed to be in the caldav/carddav paths and not the server address. Or other way around :).

For some reason with 1.1.7 autodiscovery didn't work for me with the .well-known URLs. I haven't tried with 1.1.9 yet.

edit flag offensive delete publish link more

Comments

Auto discovery with .well-known only works when owncloud is installed in the root directory of the web server. See here for more details.

And:

RFC 5785 specifies ./well-known-URIs: A well-known URI is a URI whose path component begins with the characters "/.well-known/". So it's forbidden to have something like example.org/owncloud/.well-known/. This is also explained in Appendix B: 4. Why aren't per-directory well-known locations defined? So it's not Jollas fault that auto discovery does not work on ownCloud installations that aren't installed in server root.

Yo ( 2015-09-07 11:49:31 +0300 )edit

Indeed it is installed in the root of the web server.

Earlier while owncloud was installed under /owncloud/, well-knows where configured as aliases in the root, https://server/.well-known/caldav would be redirected to /owncloud/remote.php/caldav and same for carddav.

tonza ( 2015-09-07 11:57:46 +0300 )edit
Login/Signup to Answer

Question tools

Follow
5 followers

Stats

Asked: 2015-09-07 02:48:15 +0300

Seen: 1,447 times

Last updated: Sep 07 '15