OwnCloud

ownCloud is an open source cloud software suite for remote access of calendar, address and file data. It uses a SabreDAV backend.

As of 2012-02-25 there are a number of known issues (bugs) in the SabreDAV version used by ownCloud. Please try to update the SabreDAV part of your ownCloud installation first if something doesn't work as expected. Most users reported success with SabreDAV version 1.5.8. SabreDAV version 1.6 has been reported "not working" with ownCloud 3. All known issues have been fixed in ownCloud 4. There is a new CalDAV issue with ownCloud 4, see below

Source(s): OwnCloud

Setup with ownCloud 4

In ownCloud 4 the CalDAV and CardDAV path names changed, once again. If you upgrade to ownCloud 4 you'll have to recreate the accounts in Android. You can find the correct CalDAV/CardDAV path names in settings -> personal. The path names below are just examples, please refer to your actual settings.

Source(s): OwnCloud

CalDAV-Sync

• Server URL: <servername>/owncloud/remote.php/caldav/ (see Calendar in settings -> personal in your ownCloud account)
• Use SSL: check accordingly
• Username: your login name
• Password: your password

Source(s): OwnCloud

CardDAV-Sync

• Server URL: <servername>/owncloud/remote.php/carddav/ (see Contacts in settings -> personal in your ownCloud account)
• Use SSL: check accordingly
• Username: your login name
• Password: your password

Source(s): OwnCloud

Setup with ownCloud 3

CalDAV-Sync

• Server URL: <servername>/owncloud/apps/calendar/caldav.php/calendars/
• Use SSL: check accordingly
• Username: your login name
• Password: your password

Note: The /owncloud/ part depends on your setup. If it doesn't work try /cloud/ (or whatever your ownCloud root is) instead.

Source(s): OwnCloud

CardDAV-Sync

• Server URL: <servername>/owncloud/apps/contacts/carddav.php/addressbooks/
• Use SSL: check accordingly
• Username: your login name
• Password: your password

Note: The /owncloud/ part depends on your setup. If it doesn't work try /cloud/ (or whatever your ownCloud root is) instead.

Source(s): OwnCloud

known issues

CalDAV

There is a known bug in SabreDAV (which is used by ownCloud): If your calendar contains events with certain time zone IDs that are not recognized by SabreDAV then the server returns an "internal server error" instead of a proper response to the calendar query. Currently your only option is to find those events and delete them (or change the time zone id). Please note that many desktop clients like Thunderbird Lightning and Evolution do not use "calendar query" and thus still work with ownCloud in that case. Please see [1] there is a patch linked that is reported to fix this issue. This has been fixed in ownCloud 4.

If some recurring events are missing on your phone see: [2]. Alternatively update SabreDAV in your ownCloud installation to the most recent SabreDAV release. This has been fixed in ownCloud 4 (it uses a more recent SabreDAV release).

ownCloud 4

There is a new issue with ownCloud 4. Please see TRIGGER:PT0S throws exception It's actually a bug in the SabreDAV version used by ownCloud 4. One of the comments contains a fix.

Syncing with ownCloud 4.0.4 seem to be completely broken. I got several reports of issues like this one: http://mail.kde.org/pipermail/owncloud/2012-July/004263.html here are the bug reports that seem to cover this issue oc-1199 and oc1247.

Source(s): OwnCloud

CardDAV

During my tests I noticed, that ownCloud seems to populate the vcard file with the FN (formatted name) field only and omits the N (structured name) field. On some phones this may result in improperly displayed names. Please report! This seems to be fixed in ownCloud 4

There is a report for this bug at bugs.owncloud.org: http://bugs.owncloud.org/thebuggenie/owncloud/issues/oc-8 This seems to be fixed in ownCloud 4

ownClouds contacts app is broken and creates improperly formatted vCards if you're not using the structured name editor. In that case it will put the whole name in the last name field.

Source(s): OwnCloud

Troubleshooting

Server errors

If you're getting server errors, the reason is (as the name says) located on the server. This sections aims to give you hints what to do for some known issues.

Source(s): OwnCloud

Temporary files directory not accessible

Error Message:

Notice: session_start() [function.session-start]: ps_files_cleanup_dir: opendir(/tmp) failed: Permission denied (13) in /www/htdocs/w00xxxxxx/owncloud;/lib/base.php on line 264
Sabre_DAV_Exception_NotAuthenticated No basic authentication headers were found 1.6.4

Explanation:

This happens when your hosted ownCloud has no access to the global /tmp directory.

Fix:

To fix it you have to change the temporary directory of your installation. Create a new directory and change the variable session.save_path to point there (i.e. change .htaccess to contain the following line, change the path accordingly)

php_value session.save_path /www/htdocs/w00xxxxxx/temp/

Don't forget to create that directory if it doesn't exist yet.

Source(s): OwnCloud

Trigger parsing error

Error Message:

Exception DateInterval::__construct(): Unknown or bad format (P) 1.6.2

Explanation:

That's caused by a bug in SabreDAV.

Fix:

Upgrade SabreDAV to the latest 1.6.x release or use the fix mentioned here: TRIGGER:PT0S throws exception

Source(s): OwnCloud

Time zone issue

Error Message:

Exception DateTimeZone::__construct(): Unknown or bad timezone (GMT+01.00/+02.00) 1.5.7

Explanation:

That's caused by a bug in the SabreDAV release used by ownCloud 3.x. It's not able to handle non-Olson time zone ids properly.

Fix:

Upgrade SabreDAV to the latest 1.5.x release or upgrade to ownCloud 4.x.

Source(s): OwnCloud

Upload issues

Error Message:

java.lang.Exception: could not upload new resource

Server log contains something like:

PHP Fatal error:  Call to undefined function iconv() in /var/www/htdocs/owncloud/apps/contacts/lib/vcard.php on line 200

Explanation:

iconv.so is not enabled in your php.ini.

Fix:

Enable iconv.so in your php.ini.

Source(s): OwnCloud