Add PIM sync troubleshooting guide

This commit is contained in:
Thomas Tanghus
2013-09-25 11:52:45 +02:00
parent 824120297f
commit 1e301d12fb
4 changed files with 42 additions and 3 deletions

View File

@@ -11,4 +11,5 @@ Contacts & Calendar
sync_osx
sync_thunderbird
sync_kde
troubleshooting

View File

@@ -49,5 +49,5 @@ Address book
- Go back to account information and hit Save.
Now should now find your contacts in the address book of your
iPhone.Problems have been reported for iOS 4.X. A possible solution is
at the `forum <http://forum.owncloud.org/viewtopic.php?f=3&t=71&p=2211#p2197>`_.
iPhone.
If it's still not working, have a look at the :doc:`troubleshooting` guide.

View File

@@ -12,7 +12,7 @@ The setup is basically the same as with iOS using the path **ADDRESS/remote.php/
#. Go back to the folder window from step 2. You will now see a newly created folder with another long string as its name.
#. Navigate to the newly created folder and edit the **Configuration.plist** with your favorite text editor.
#. Search for a section looking like this::
<key>servername</key> <string>http://:0(null)</string> <key>username</key> <string>Whatever_you_entered_before</string>
8. Make it look like this. Please note that the :80 after **YOUR_DOMAIN** is important::
@@ -25,6 +25,8 @@ The setup is basically the same as with iOS using the path **ADDRESS/remote.php/
11. You may have to restart Address Book once more. After this, it should work.
If it's still not working, have a look at the :doc:`troubleshooting` guide.
There is also an easy `HOWTO`_ in the forum.

View File

@@ -0,0 +1,36 @@
Troubleshooting
===============
Service discovery
-----------------
Some clients - especially iOS - have problems finding the proper sync URL, even when explicitly
configured to use it.
There are several techniques to remedy this, which are described extensively at the
`Sabre DAV website <http://code.google.com/p/sabredav/wiki/ServiceDiscovery>`_.
Below is what have proven to work with iOS including iOS 7.
If your ownCloud instance is installed in a sub-folder under the web servers document root, and
the client has difficulties finding the Cal- or CardDAV end-points, configure your web server to
redirect from a "well-know" URL to the one used by ownCloud.
When using the Apache web server this is easily achieved using a :file:`.htaccess` file in the document
root of your site.
Say your instance is located in the ``owncloud`` folder, so the URL to it is ``ADDRESS/owncloud``,
create or edit the :file:`.htaccess` file and add the following lines::
Redirect 301 /.well-known/carddav /owncloud/remote.php/carddav
Redirect 301 /.well-known/caldav /owncloud/remote.php/caldav
If you use Nginx as web server, the setting looks something like::
url.redirect = (
"^/.well-known/carddav" => "/owncloud/remote.php/carddav",
"^/.well-known/caldav" => "/owncloud/remote.php/caldav",
)
Now change the URL in the client settings to just use ``ADDRESS`` instead of e.g. ``ADDRESS/remote.php/carddav/principals/username``.
This problem is being discussed in the `forum <http://forum.owncloud.org/viewtopic.php?f=3&t=71&p=2211#p2197>`_.