Manual Installation on Linux

Installing ownCloud on Linux from our Open Build Service packages is the preferred method (see Preferred Linux Installation Method). These are maintained by ownCloud engineers, and you can use your package manager to keep your ownCloud server up-to-date.


Enterprise customers should refer to Installing & Upgrading ownCloud Enterprise Edition

If there are no packages for your Linux distribution, or you prefer installing from the source tarball, you can setup ownCloud from scratch using a classic LAMP stack (Linux, Apache, MySQL/MariaDB, PHP). This document provides a complete walk-through for installing ownCloud on Ubuntu 14.04 LTS Server with Apache and MariaDB, using the ownCloud .tar archive.


Admins of SELinux-enabled distributions such as CentOS, Fedora, and Red Hat Enterprise Linux may need to set new rules to enable installing ownCloud. See SELinux Configuration Tips for a suggested configuration.


The ownCloud .tar archive contains all of the required PHP modules. This section lists all required and optional PHP modules. Consult the PHP manual for more information on modules. Your Linux distribution should have packages for all required modules. You can check the precense of a module by typing php -m | grep -i <module_name>. If you get a result, the module is present.


  • php5 (>= 5.4)
  • PHP module ctype
  • PHP module dom
  • PHP module GD
  • PHP module iconv
  • PHP module JSON
  • PHP module libxml
  • PHP module mb multibyte
  • PHP module posix
  • PHP module SimpleXML
  • PHP module XMLWriter
  • PHP module zip
  • PHP module zlib

Database connectors (pick the one for your database:)

  • PHP module sqlite (>= 3, usually not recommended for performance reasons)
  • PHP module pdo_mysql (MySQL/MariaDB)
  • PHP module pgsql (requires PostgreSQL >= 9.0)

Recommended packages:

  • PHP module curl (highly recommended, some functionality, e.g. HTTP user authentication, depends on this)
  • PHP module fileinfo (highly recommended, enhances file analysis performance)
  • PHP module bz2 (recommended, required for extraction of apps)
  • PHP module intl (increases language translation performance and fixes sorting of non-ASCII characters)
  • PHP module mcrypt (increases file encryption performance)
  • PHP module openssl (required for accessing HTTPS resources)

Required for specific apps:

  • PHP module ldap (for LDAP integration)
  • php5-libsmbclient (SMB/CIFS integration)
  • PHP module ftp (for FTP storage / external user authentication)
  • PHP module imap (for external user authentication)

Recommended for specific apps (optional):

  • PHP module exif (for image rotation in pictures app)
  • PHP module gmp (for SFTP storage)

For enhanced server performance (optional) select one of the following memcaches:

  • PHP module apc
  • PHP module apcu
  • PHP module memcached
  • PHP module redis (required for Transactional File Locking)

See Configuring Memory Caching to learn how to select and configure a memcache.

For preview generation (optional):

  • PHP module imagick
  • avconv or ffmpeg
  • OpenOffice or LibreOffice

For command line processing (optional):

  • PHP module pcntl (enables command interruption by pressing ctrl-c)

You don’t need the WebDAV module for your Web server (i.e. Apache’s mod_webdav), as ownCloud has a built-in WebDAV server of its own, SabreDAV. If mod_webdav is enabled you must disable it for ownCloud. (See Apache Web Server Configuration for an example configuration.)

Example Installation on Ubuntu 14.04 LTS Server

On a machine running a pristine Ubuntu 14.04 LTS server, install the required and recommended modules for a typical ownCloud installation, using Apache and MariaDB, by issuing the following commands in a terminal:

apt-get install apache2 mariadb-server libapache2-mod-php5
apt-get install php5-gd php5-json php5-mysql php5-curl
apt-get install php5-intl php5-mcrypt php5-imagick
  • This installs the packages for the ownCloud core system. libapache2-mod-php5 provides the following PHP extensions: bcmath bz2 calendar Core ctype date dba dom ereg exif fileinfo filter ftp gettext hash iconv libxml mbstring mhash openssl pcre Phar posix Reflection session shmop SimpleXML soap sockets SPL standard sysvmsg sysvsem sysvshm tokenizer wddx xml xmlreader xmlwriter zip zlib. If you are planning on running additional apps, keep in mind that they might require additional packages. See Prerequisites for details.
  • At the installation of the MySQL/MariaDB server, you will be prompted to create a root password. Be sure to remember your password as you will need it during ownCloud database setup.

Now download the archive of the latest ownCloud version:

  • Go to the ownCloud Download Page.

  • Go to Download ownCloud Server > Download > Archive file for server owners and download either the tar.bz2 or .zip archive.

  • This downloads a file named owncloud-x.y.z.tar.bz2 or (where x.y.z is the version number).

  • Download its corresponding checksum file, e.g. owncloud-x.y.z.tar.bz2.md5, or owncloud-x.y.z.tar.bz2.sha256.

  • Verify the MD5 or SHA256 sum:

    md5sum -c owncloud-x.y.z.tar.bz2.md5 < owncloud-x.y.z.tar.bz2
    sha256sum -c owncloud-x.y.z.tar.bz2.sha256 < owncloud-x.y.z.tar.bz2
    md5sum  -c <
    sha256sum  -c <
  • You may also verify the PGP signature:

    gpg --import owncloud.asc
    gpg --verify owncloud-x.y.z.tar.bz2.asc owncloud-x.y.z.tar.bz2
  • Now you can extract the archive contents. Run the appropriate unpacking command for your archive type:

    tar -xjf owncloud-x.y.z.tar.bz2
  • This unpacks to a single owncloud directory. Copy the ownCloud directory to its final destination. When you are running the Apache HTTP server you may safely install ownCloud in your Apache document root:

    cp -r owncloud /path/to/webserver/document-root

    where /path/to/webserver/document-root is replaced by the document root of your Web server:

    cp -r owncloud /var/www

On other HTTP servers it is recommended to install ownCloud outside of the document root.


If your ownCloud installation fails and you see this in your ownCloud log:

An unhandled exception has been thrown: exception ‘PDOException’ with message
'SQLSTATE[HY000]: General error: 1665 Cannot execute statement: impossible to
write to binary log since BINLOG_FORMAT = STATEMENT and at least one table
uses a storage engine limited to row-based logging. InnoDB is limited to
row-logging when transaction isolation level is READ COMMITTED or READ

See MySQL / MariaDB with Binary Logging Enabled.

Apache Web Server Configuration

On Debian, Ubuntu, and their derivatives, Apache installs with a useful configuration so all you have to do is create a /etc/apache2/sites-available/owncloud.conf file with these lines in it, replacing the Directory and other filepaths with your own filepaths:

Alias /owncloud "/var/www/owncloud/"

<Directory /var/www/owncloud/>
  Options +FollowSymlinks
  AllowOverride All

 <IfModule mod_dav.c>
  Dav off

 SetEnv HOME /var/www/owncloud
 SetEnv HTTP_HOME /var/www/owncloud


Then create a symlink to /etc/apache2/sites-enabled:

ln -s /etc/apache2/sites-available/owncloud.conf /etc/apache2/sites-enabled/owncloud.conf

Additional Apache Configurations

  • For ownCloud to work correctly, we need the module mod_rewrite. Enable it by running:

    a2enmod rewrite

    Additional recommended modules are mod_headers, mod_env, mod_dir and mod_mime:

    a2enmod headers
    a2enmod env
    a2enmod dir
    a2enmod mime

    If you’re running mod_fcgi instead of the standard mod_php also enable:

    a2enmod setenvif
  • You must disable any server-configured authentication for ownCloud, as it uses Basic authentication internally for DAV services. If you have turned on authentication on a parent folder (via e.g. an AuthType Basic directive), you can turn off the authentication specifically for the ownCloud entry. Following the above example configuration file, add the following line in the <Directory section:

    Satisfy Any
  • When using SSL, take special note of the ServerName. You should specify one in the server configuration, as well as in the CommonName field of the certificate. If you want your ownCloud to be reachable via the internet, then set both of these to the domain you want to reach your ownCloud server.

  • Now restart Apache:

    service apache2 restart
  • If you’re running ownCloud in a subdirectory and want to use CalDAV or CardDAV clients make sure you have configured the correct Service discovery URLs.

Enabling SSL


You can use ownCloud over plain HTTP, but we strongly encourage you to use SSL/TLS to encrypt all of your server traffic, and to protect user’s logins and data in transit.

Apache installed under Ubuntu comes already set-up with a simple self-signed certificate. All you have to do is to enable the ssl module and the default site. Open a terminal and run:

a2enmod ssl
a2ensite default-ssl
service apache2 reload


Self-signed certificates have their drawbacks - especially when you plan to make your ownCloud server publicly accessible. You might want to consider getting a certificate signed by a commercial signing authority. Check with your domain name registrar or hosting service for good deals on commercial certificates.

Installation Wizard

After restarting Apache you must complete your installation by running either the graphical Installation Wizard, or on the command line with the occ command. To enable this, temporarily change the ownership on your ownCloud directories to your HTTP user (see Setting Strong Directory Permissions to learn how to find your HTTP user):

chown -R www-data:www-data /var/www/owncloud/


Admins of SELinux-enabled distributions may need to write new SELinux rules to complete their ownCloud installation; see SELinux Configuration Tips.

To use occ see Installing ownCloud From the Command Line.

To use the graphical Installation Wizard see Installation Wizard.

Setting Strong Directory Permissions

After completing installation, you must immediately set the directory permissions in your ownCloud installation as strictly as possible for stronger security. Please refer to Setting Strong Directory Permissions.

Now your ownCloud server is ready to use.

SELinux Configuration Tips

See SELinux Configuration for a suggested configuration for SELinux-enabled distributions such as Fedora and CentOS.

php.ini Configuration Notes

Keep in mind that changes to php.ini may have to be done on more than one ini file. This can be the case, for example, for the date.timezone setting.

php.ini - used by the Web server:

or ...

php.ini - used by the php-cli and so by ownCloud CRON jobs:


php-fpm Configuration Notes

Security: Use at least PHP => 5.5.22 or >= 5.6.6

Due to a bug with security implications in older PHP releases with the handling of XML data you are highly encouraged to run at least PHP 5.5.22 or 5.6.6 when in a threaded environment.

System environment variables

When you are using php-fpm, system environment variables like PATH, TMP or others are not automatically populated in the same way as when using php-cli. A PHP call like getenv('PATH'); can therefore return an empty result. So you may need to manually configure environment varibles in the appropropriate php-fpm ini/config file.

Here are some example root paths for these ini/config files:

Ubuntu/Mint CentOS/Red Hat/Fedora
/etc/php5/fpm/ /etc/php-fpm.d/

In both examples, the ini/config file is called www.conf, and depending on the distro version or customizations you have made, it may be in a subdirectory.

Usually, you will find some or all of the environment variables already in the file, but commented out like this:

;env[PATH] = /usr/local/bin:/usr/bin:/bin
;env[TMP] = /tmp
;env[TMPDIR] = /tmp
;env[TEMP] = /tmp

Uncomment the appropriate existing entries. Then run printenv PATH to confirm your paths, for example:

$ printenv PATH

If any of your system environment variables are not present in the file then you must add them.

When you are using shared hosting or a control panel to manage your ownCloud VM or server, the configuration files are almost certain to be located somewhere else, for security and flexibility reasons, so check your documentation for the correct locations.

Please keep in mind that it is possible to create different settings for php-cli and php-fpm, and for different domains and Web sites. The best way to check your settings is with PHP Version and Information.

Maximum upload size

If you want to increase the maximum upload size, you will also have to modify your php-fpm configuration and increase the upload_max_filesize and post_max_size values. You will need to restart php5-fpm and your HTTP server in order for these changes to be applied.

.htaccess notes for Apache

ownCloud comes with its own owncloud/.htaccess file. Because php-fpm can’t read PHP settings in .htaccess these settings and permissions must be set in the owncloud/.user.ini file.

All documentation licensed under the Creative Commons Attribution 3.0 Unported license.