Upgrade ownCloud

NOTE: We are in the process of modifying the file structure and configuration for many Bitnami stacks. On account of these changes, the file paths stated in this guide may change depending on whether your Bitnami stack uses native Linux system packages (Approach A), or if it is a self-contained installation (Approach B). To identify your Bitnami installation type and what approach to follow, run the command below:

The output of the command indicates which approach (A or B) is used by the installation, and will allow you to identify the paths, configuration and commands to use in this guide. Refer to the FAQ for more information on these changes.

It is strongly recommended to create a backup before starting the update process. If you have important data, create and try to restore a backup to ensure that everything works properly.

Approach A: Bitnami installations using system packages

Upgrade ownCloud and all stack components (recommended)

Log in to the server console via SSH. Please check our FAQ for instructions on how to connect to your server through SSH.

Backup the bitnami_owncloud database as described on the MySQL page.

Compress and backup the current installation data in /bitnami/owncloud:

Download the backup files owncloud-backup.tar.gz and backup.sql using SFTP. Refer to the FAQ for more information on this.

Launch a new Bitnami ownCloud Stack with the latest version.

Upload via SFTP the backup files owncloud-backup.tar.gz and backup.sql to the new server.

Log in to the new server console via SSH.

Restore the backup.sql database backup as described on the MySQL page.

Locate and store the original database password for the new installation (from now on it will be referred to as DBPASSWORD):

Restore the owncloud-backup.tar.gz backup files in the new Bitnami ownCloud Stack. You can use the commands below:

Edit the backup /opt/bitnami/owncloud/config/config.php file and change the dbpassword parameter to use the value of the new database password DBPASSWORD, which was obtained previously:

That’s it! You updated the whole stack!

Upgrade only ownCloud using the built-in update tool

ownCloud already ships an “Updater” tool installed that allows upgrading the ownCloud application from the admin panel directly. For security reasons, some ownCloud files do not have write access for the web server user, but this will be required if you want to upgrade the application.

Before running the “Updater” app, run the following commands to change the ownership of the required files in your installation:

Run the upgrade process from the admin panel by navigating to “Settings -> General -> Updater -> Open Updater” and running the upgrade process.

If the upgrade worked well, restore the permissions:

That’s it! You updated the application! You can find more information about the upgrade process in the official ownCloud documentation.

Upgrade only ownCloud manually

For security reasons, some ownCloud files do not have write access for the web server user, but this will be required if you want to upgrade the application.

Before running the upgrade process, run the following commands to change the ownership of some required files in your installation:

Enable maintenance mode:

Backup the bitnami_owncloud database as described on the MySQL page.

Download and uncompress the latest version of ownCloud from ownCloud Official Website. For example (for version 10.0.2), use the commands below:

Compress and backup the current installation data in /bitnami/owncloud:

Run the upgrade command (this could take a few minutes) and disable maintenance mode:

If the upgrade worked well, restore the permissions:

That’s it! You updated the application! You can find more information about the upgrade process in the official ownCloud documentation.

Approach B: Self-contained Bitnami installations

Upgrade ownCloud and all stack components (recommended)

Log in to the server console via SSH. Please check our FAQ for instructions on how to connect to your server through SSH.

Create a directory to save all the data you need to backup.

Backup the bitnami_owncloud database as described on the MySQL page.

Copy the conf/, data and htdocs//config directories to your backup directory. You can use the commands below:

Compress the backup directory:

Download the backup files owncloud-backup.tar.gz and backup.sql using SFTP. Refer to the FAQ for more information on this.

Launch a new Bitnami ownCloud Stack with the latest version.

Upload via SFTP the backup files owncloud-backup.tar.gz and backup.sql to the new server.

Log in to the new server console via SSH.

Restore the backup.sql database backup as described on the MySQL page.

Edit the backup

/owncloud-backup/config/config.php file and change the dbpassword parameter using the new one that can be found in the new /opt/bitnami/apps/owncloud/htdocs/config/config.php file. To do so, use an editor to modify it manually or the commands below:

Restore the backup files in the new Bitnami ownCloud Stack. You can use the commands below:

Restore the permissions.

Restore the Apache configuration files in the new ownCloud stack. Use the command below:

That’s it! You updated the whole stack!

Upgrade only ownCloud using the built-in update tool

ownCloud already ships an “Updater” tool installed that allows upgrading the ownCloud application from the admin panel directly. For security reasons, ownCloud files do not have write access for the web server user, but this will be required if you want to upgrade the application.

Before running the “Updater” app, run the following commands to change the ownership of the required files in your installation:

Run the upgrade process from the admin panel by navigating to “Settings -> General -> Updater -> Open Updater” and running the upgrade process.

If the upgrade worked well, restore the permissions:

That’s it! You updated the application! You can find more information about the upgrade process in the official ownCloud documentation.

Upgrade only ownCloud manually

Enable maintenance mode:

Backup the bitnami_owncloud database as described on the MySQL page.

Download and uncompress the latest version of ownCloud from ownCloud Official Website. For example (for version 10.0.2), use the commands below:

Backup the current installation and substitute it with the new one:

Restore the permissions:

Run the upgrade command (this could take a few minutes) and disable maintenance mode:

Restore the strong permissions configuration:

That’s it! You updated the application! You can find more information about the upgrade process in the official ownCloud documentation.

Upgrade ownCloud

NOTE: We are in the process of modifying the file structure and configuration for many Bitnami stacks. On account of these changes, the file paths stated in this guide may change depending on whether your Bitnami stack uses native Linux system packages (Approach A), or if it is a self-contained installation (Approach B). To identify your Bitnami installation type and what approach to follow, run the command below:

The output of the command indicates which approach (A or B) is used by the installation, and will allow you to identify the paths, configuration and commands to use in this guide. Refer to the FAQ for more information on these changes.

It is strongly recommended to create a backup before starting the update process. If you have important data, create and try to restore a backup to ensure that everything works properly.

Approach A: Bitnami installations using system packages

Upgrade ownCloud and all stack components (recommended)

Log in to the server console via SSH. Please check our FAQ for instructions on how to connect to your server through SSH.

Backup the bitnami_owncloud database as described on the MySQL page.

Compress and backup the current installation data in /bitnami/owncloud:

Download the backup files owncloud-backup.tar.gz and backup.sql using SFTP. Refer to the FAQ for more information on this.

Launch a new Bitnami ownCloud Stack with the latest version.

Upload via SFTP the backup files owncloud-backup.tar.gz and backup.sql to the new server.

Log in to the new server console via SSH.

Restore the backup.sql database backup as described on the MySQL page.

Locate and store the original database password for the new installation (from now on it will be referred to as DBPASSWORD):

Restore the owncloud-backup.tar.gz backup files in the new Bitnami ownCloud Stack. You can use the commands below:

Edit the backup /opt/bitnami/owncloud/config/config.php file and change the dbpassword parameter to use the value of the new database password DBPASSWORD, which was obtained previously:

That’s it! You updated the whole stack!

Upgrade only ownCloud using the built-in update tool

ownCloud already ships an “Updater” tool installed that allows upgrading the ownCloud application from the admin panel directly. For security reasons, some ownCloud files do not have write access for the web server user, but this will be required if you want to upgrade the application.

Before running the “Updater” app, run the following commands to change the ownership of the required files in your installation:

Run the upgrade process from the admin panel by navigating to “Settings -> General -> Updater -> Open Updater” and running the upgrade process.

If the upgrade worked well, restore the permissions:

That’s it! You updated the application! You can find more information about the upgrade process in the official ownCloud documentation.

Upgrade only ownCloud manually

For security reasons, some ownCloud files do not have write access for the web server user, but this will be required if you want to upgrade the application.

Before running the upgrade process, run the following commands to change the ownership of some required files in your installation:

Enable maintenance mode:

Backup the bitnami_owncloud database as described on the MySQL page.

Download and uncompress the latest version of ownCloud from ownCloud Official Website. For example (for version 10.0.2), use the commands below:

Compress and backup the current installation data in /bitnami/owncloud:

Run the upgrade command (this could take a few minutes) and disable maintenance mode:

If the upgrade worked well, restore the permissions:

That’s it! You updated the application! You can find more information about the upgrade process in the official ownCloud documentation.

Approach B: Self-contained Bitnami installations

Upgrade ownCloud and all stack components (recommended)

Log in to the server console via SSH. Please check our FAQ for instructions on how to connect to your server through SSH.

Create a directory to save all the data you need to backup.

Backup the bitnami_owncloud database as described on the MySQL page.

Copy the conf/, data and htdocs//config directories to your backup directory. You can use the commands below:

Compress the backup directory:

Download the backup files owncloud-backup.tar.gz and backup.sql using SFTP. Refer to the FAQ for more information on this.

Launch a new Bitnami ownCloud Stack with the latest version.

Upload via SFTP the backup files owncloud-backup.tar.gz and backup.sql to the new server.

Log in to the new server console via SSH.

Restore the backup.sql database backup as described on the MySQL page.

Edit the backup

/owncloud-backup/config/config.php file and change the dbpassword parameter using the new one that can be found in the new /opt/bitnami/apps/owncloud/htdocs/config/config.php file. To do so, use an editor to modify it manually or the commands below:

Restore the backup files in the new Bitnami ownCloud Stack. You can use the commands below:

Restore the permissions.

Restore the Apache configuration files in the new ownCloud stack. Use the command below:

That’s it! You updated the whole stack!

Upgrade only ownCloud using the built-in update tool

ownCloud already ships an “Updater” tool installed that allows upgrading the ownCloud application from the admin panel directly. For security reasons, ownCloud files do not have write access for the web server user, but this will be required if you want to upgrade the application.

Before running the “Updater” app, run the following commands to change the ownership of the required files in your installation:

Run the upgrade process from the admin panel by navigating to “Settings -> General -> Updater -> Open Updater” and running the upgrade process.

If the upgrade worked well, restore the permissions:

That’s it! You updated the application! You can find more information about the upgrade process in the official ownCloud documentation.

Upgrade only ownCloud manually

Enable maintenance mode:

Backup the bitnami_owncloud database as described on the MySQL page.

Download and uncompress the latest version of ownCloud from ownCloud Official Website. For example (for version 10.0.2), use the commands below:

Backup the current installation and substitute it with the new one:

Restore the permissions:

Run the upgrade command (this could take a few minutes) and disable maintenance mode:

Restore the strong permissions configuration:

That’s it! You updated the application! You can find more information about the upgrade process in the official ownCloud documentation.

Installing the Desktop Synchronization Client

You can download the latest version of the ownCloud Desktop Synchronization Client from the ownCloud download page. There are clients for Linux, macOS, and Microsoft Windows.

Installation on Mac OS X and Windows is the same as for any software application: download the program and then double-click it to launch the installation, and then follow the installation wizard. After it is installed and configured the sync client will automatically keep itself updated; see autoupdate for more information.

Linux users must follow the instructions on the download page to add the appropriate repository for their Linux distribution, install the signing key, and then use their package managers to install the desktop sync client. Linux users will also update their sync clients via package manager, and the client will display a notification when an update is available.

Linux users must also have a password manager enabled, such as GNOME Keyring or KWallet, so that the sync client can login automatically.

You will also find links to source code archives and older versions on the download page.

System Requirements

Windows 7+ (x86 with 32-bit or x86-64; Native WinVFS available for Windows 10 version 1709 or later)

macOS 10.12+ (x86-64 or Apple M in Rosetta 2 emulation; unsupported legacy builds for Mac OS X 10.10 & 10.11 available)

CentOS 7.6+ & 8 (x86-64)

Debian 9.0 & 10 (x86-64)

Fedora 30 & 31 & 32 (x86-64)

Ubuntu 18.04 & 19.04 & 19.10 & 20.04 (x86-64)

openSUSE Leap 15.0 & 15.1 & 15.2 (x86-64)

For Linux distributions, we support, if technically feasible, the latest 2 versions per platform and the previous Ubuntu LTS.

Customizing the Windows Installation

If you just want to install ownCloud Desktop Synchronization Client on your local system, you can simply launch the .msi file and configure it in the wizard that pops up.

Features

The MSI installer provides several features that can be installed or removed individually, which you can also control via command-line, if you are automating the installation, then run the following command:

The command will install the ownCloud Desktop Synchronization Client into the default location with the default features enabled. If you want to disable, e.g., desktop shortcut icons you can simply change the above command to the following:

See the following table for a list of available features:

The actual client

Adds a shortcut to the desktop.

Adds shortcuts to the start menu.

Adds Explorer integration

Installation

You can also choose to only install the client itself by using the following command:

If you for instance want to install everything but the DesktopShortcut and the ShellExtensions feature, you have two possibilities:

You explicitly name all the features you actually want to install (whitelist) where Client is always installed anyway.

You pass the NO_DESKTOP_SHORTCUT and NO_SHELL_EXTENSIONS properties.

Feature	Enabled by default	Description	Property to disable.

The ownCloud .msi remembers these properties, so you don’t need to specify them on upgrades.

You cannot use these to change the installed features, if you want to do that, see the next section.

Changing Installed Features

You can change the installed features later by using REMOVE and ADDDEFAULT properties.

If you want to add the desktop shortcut later, run the following command:

If you want to remove it, simply run the following command:

Windows keeps track of the installed features and using REMOVE or ADDDEFAULT will only affect the mentioned features.

Compare REMOVE and ADDDEFAULT on the Windows Installer Guide.

You cannot specify REMOVE on initial installation as it will disable all features.

Installation Folder

You can adjust the installation folder by specifying the INSTALLDIR property like this.

Be careful when using PowerShell instead of cmd.exe , it can be tricky to get the whitespace escaping right there. Specifying the INSTALLDIR like this only works on first installation, you cannot simply re-invoke the .msi with a different path. If you still need to change it, uninstall it first and reinstall it with the new path.

Disabling Automatic Updates.

To disable automatic updates, you can pass the SKIPAUTOUPDATE property.

Launch After Installation

To launch the client automatically after installation, you can pass the. LAUNCH property.

This option also removes the checkbox to let users decide if they want to launch the client for non passive/quiet mode.

This option does not have any effect without GUI.

No Reboot After Installation

The ownCloud Client schedules a reboot after installation to make sure the Explorer extension is correctly (un)loaded. If you’re taking care of the reboot yourself, you can set the REBOOT property.

This will make msiexec exit with error ERROR_SUCCESS_REBOOT_REQUIRED (3010). If your deployment tooling interprets this as an actual error and you want to avoid that, you may want to set the DO_NOT_SCHEDULE_REBOOT instead.

Installation Wizard

The installation wizard takes you step-by-step through configuration options and account setup. First you need to enter the URL of your ownCloud server.

Enter your ownCloud login on the next screen.

On the «Local Folder Option» screen you may sync all of your files on the ownCloud server, or select individual folders. The default local sync folder is ownCloud , in your home directory. You may change this as well.

When you have completed selecting your sync folders, click the «Connect» button at the bottom right. The client will attempt to connect to your ownCloud server, and when it is successful you’ll see two buttons:

One to connect to your ownCloud Web GUI.

One to open your local folder.

It will also start synchronizing your files.