If you have trouble installing, configuring or maintaining ownCloud, please refer to our community support channels:
Note
The ownCloud forums have a FAQ page where each topic corresponds to typical mistakes or frequently occurring issues
Please understand that all these channels essentially consist of users like you helping each other out. Consider helping others out where you can, to contribute back for the help you get. This is the only way to keep a community like ownCloud healthy and sustainable!
If you are using ownCloud in a business or otherwise large scale deployment, note that ownCloud Inc. offers the Enterprise Subscription with commercial support options.
If you think you have found a bug in ownCloud, please:
If you can’t find a solution, please use our bugtracker.
Check the ownCloud System Requirements, especially supported browser versions.
When you see warnings about code integrity, refer to Code Signing.
It might be possible that 3rd party / non-shipped apps are causing various different issues. Always disable 3rd party apps before upgrades, and for troubleshooting. Please refer to the Apps Commands on how to disable an app from command line.
In a standard ownCloud installation the log level is set to Normal. To find any issues you need to raise the log level to All in your config.php file, or to Everything on your ownCloud Admin page. Please see Logging Configuration for more information on these log levels.
Some logging - for example JavaScript console logging - needs manually editing the configuration file. Edit config/config.php and add define('DEBUG', true);:
<?php
define('DEBUG',true);
$CONFIG = array (
... configuration goes here ...
);
For JavaScript issues you will also need to view the javascript console. All major browsers have developer tools for viewing the console, and you usually access them by pressing F12. For Firefox we recommend to installing the Firebug extension.
Note
The logfile of ownCloud is located in the data directory owncloud/data/owncloud.log.
You will need to know your PHP version and configurations. To do this, create a plain-text file named phpinfo.php and place it in your Web root, for example /var/www/html/phpinfo.php. (Your Web root may be in a different location; your Linux distribution documentation will tell you where.) This file contains just this line:
<?php phpinfo(); ?>
Open this file in a Web browser by pointing your browser to localhost/phpinfo.php:
Your PHP version is at the top, and the rest of the page contains abundant system information such as active modules, active .ini files, and much more. When you are finished reviewing your information you must delete phpinfo.php, or move it outside of your Web directory, because it is a security risk to expose such sensitive data.
Note
The data directory on the server is exclusive to ownCloud and must not be modified manually.
Disregarding this can lead to unwanted behaviours like:
If you need to directly upload files from the same server please use a WebDAV command line client like cadaver to upload files to the WebDAV interface at:
https://example.com/owncloud/remote.php/dav
Some common problems / error messages found in your logfiles as described above:
When having issues the first step is to check the logfiles provided by PHP, the Web server and ownCloud itself.
Note
In the following the paths to the logfiles of a default Debian installation running Apache2 with mod_php is assumed. On other Web servers, Linux distros or operating systems they can differ.
Note
Lighttpd is not supported with ownCloud, and some ownCloud features may not work at all on Lighttpd.
There are some Web server or PHP modules which are known to cause various problems like broken up-/downloads. The following shows a draft overview of these modules:
ownCloud uses SabreDAV, and the SabreDAV documentation is comprehensive and helpful.
See:
There is also a well maintained FAQ thread available at the ownCloud Forums which contains various additional information about WebDAV problems.
Some clients - especially on iOS/Mac OS X - have problems finding the proper sync URL, even when explicitly configured to use it.
If you want to use CalDAV or CardDAV clients together with ownCloud it is important to have a correct working setup of the following URLs:
Those need to be redirecting your clients to the correct DAV endpoints. If running ownCloud at the document root of your Web server the correct URL is:
https://example.com/remote.php/dav
and if running in a subfolder like owncloud:
https://example.com/owncloud/remote.php/dav
For the first case the .htaccess file shipped with ownCloud should do this work for your when running Apache. You only need to make sure that your Web server is using this file. When running nginx please refer to the Nginx Configuration example.
If your ownCloud instance is installed in a subfolder called owncloud and you’re running Apache create or edit the .htaccess file within the document root of your Web server and add the following lines:
Redirect 301 /.well-known/carddav /owncloud/remote.php/dav
Redirect 301 /.well-known/caldav /owncloud/remote.php/dav
Now change the URL in the client settings to just use:
https://example.com
instead of e.g.
https://example.com/owncloud/remote.php/dav/principals/username.
There are also several techniques to remedy this, which are described extensively at the Sabre DAV website.
If you get an error like:
PATCH https://example.com/remote.php/dav HTTP/1.0 501 Not Implemented
it is likely caused by one of the following reasons:
Some services like Cloudflare can cause issues by minimizing JavaScript and loading it only when needed. When having issues like a not working login button or creating new users make sure to disable such services first.