Bitnami ownCloud Installer

NOTE: Before running the commands shown on this page, you should load the Bitnami stack environment by executing the installdir/use_APPNAME script (Linux and Mac OS X) or by clicking the shortcut in the Start Menu under "Start -> Bitnami APPNAME Stack -> Application console" (Windows). Learn more.
NOTE: When running the commands shown on this page, replace the installdir placeholder with the full installation directory for your Bitnami stack.

Description

ownCloud is a file storage and sharing server that is hosted in your own cloud account. Access, update, and sync your photos, files, calendars, and contacts on any device, on a platform that you own.

First steps with the Bitnami ownCloud Stack

Welcome to your new Bitnami application! Here are a few questions (and answers!) you might need when first starting with your application.

What are the system requirements?

Before you download and install your application, check that your system meets these requirements.

How do I install the Bitnami ownCloud Stack?

Windows, OS X and Linux installer
  • Download the executable file for the Bitnami ownCloud Stack from the Bitnami website.

  • Run the downloaded file:

    • On Linux, give the installer executable permissions and run the installation file in the console.
    • On other platforms, double-click the installer and follow the instructions shown.

Check the FAQ instructions on how to download and install a Bitnami Stack for more details.

The application will be installed to the following default directories:

Operating System Directory
Windows C:\Bitnami\APPNAME-VERSION
Mac OS X /Applications/APPNAME-VERSION
Linux /opt/APPNAME-VERSION (running as root user)
OS X VM
  • Download the OS X VM file for the Bitnami ownCloud Stack from the Bitnami website.
  • Begin the installation process by double-clicking the image file and dragging the WordPress OS X VM icon to the Applications folder.
  • Launch the VM by double-clicking the icon in the Applications folder.

What credentials do I need?

You need application credentials, consisting of a username and password. These credentials allow you to log in to your new Bitnami application.

What is the administrator username set for me to log in to the application for the first time?

  • For Windows, Linux and OS X installers, the username was configured by you when you first installed the application.
  • For OS X VMs, the username can be obtained by clicking the Bitnami badge at the bottom right corner of the application welcome page.

What is the administrator password?

  • For Windows, Linux and OS X installers, the password was configured by you when you first installed the application.
  • For OS X VMs, the password can be obtained by clicking the Bitnami badge at the bottom right corner of the application welcome page.

How to start or stop the services?

Linux

Bitnami native installers include a graphical tool to manage services. This tool is named manager-linux-x64.run on Linux and is located in the installation directory. To use this tool, double-click the file and then use the graphical interface to start, stop or restart services. Server log messages can be checked in the "Server Events" tab.

Management tool

The native installer also includes a command-line script to start, stop and restart applications, named ctlscript.sh. This script can be found in the installation directory and accepts the options start, stop, restart, and status. To use it, log in to the server console and execute it following the examples below:

  • Call it without any service names to start all services:

      $ sudo installdir/ctlscript.sh start
    
  • Use it to restart a specific service only by passing the service name as argument - for example, mysql, postgresql or apache:

      $ sudo installdir/ctlscript.sh restart mysql
      $ sudo installdir/ctlscript.sh restart postgresql
      $ sudo installdir/ctlscript.sh restart apache
    
  • Obtain current status of all services:

      $ installdir/ctlscript.sh status
    

The list of available services varies depending on the required components for each application.

Mac OS X

Bitnami native installers include a graphical tool to manage services. This tool is named manager-osx on Mac OS X and is located in the installation directory. To use this tool, double-click the file and then use the graphical interface to start, stop or restart services. Server log messages can be checked in the "Server Events" tab.

Management tool

The native installer also includes a command-line script to start, stop and restart applications, named ctlscript.sh. This script can be found in the installation directory and accepts the options start, stop, restart, and status. To use it, log in to the server console and execute it following the examples below:

  • Call it without any service names to start all services:

    $ sudo installdir/ctlscript.sh start
    
  • Use it to restart a specific service only by passing the service name as argument - for example, mysql or apache:

     $ sudo installdir/ctlscript.sh restart mysql
     $ sudo installdir/ctlscript.sh restart apache
    
  • Obtain current status of all services:

     $ installdir/ctlscript.sh status
    

The list of available services varies depending on the required components for each application.

NOTE: If you are using the stack manager for Mac OS X-VM, please check the following blog post to learn how to manage services from its graphical tool.

Windows

Bitnami native installers include a graphical tool to manage services. This tool is named manager-windows.exe on Windows and is located in the installation directory. To use this tool, double-click the file and then use the graphical interface to start, stop or restart services. Server log messages can be checked in the "Server Events" tab.

Management tool

The Windows native installer creates shortcuts to start and stop services created in the Start Menu, under "Programs -> Bitnami APPNAME Stack -> Bitnami Service". Servers can also be managed from the Windows "Services" control panel. Services are named using the format APPNAMESERVICENAME, where APPNAME is a placeholder for the application name and SERVICENAME is a placeholder for the service name. For example, the native installer for the Bitnami WordPress Stack installs services named wordpressApache and wordpressMySQL.

These services will be automatically started during boot. To modify this behaviour, refer to the section on disabling services on Windows.

How to configure outbound email settings?

This is required so the application can send notifications via email.

Edit the installdir/apps/owncloud/htdocs/config/config.php and add the following at the end of the file. This example uses a Gmail account. Replace USERNAME and PASSWORD with your Gmail account username and password respectively.

...
"mail_smtpmode" => 'smtp',
"mail_smtphost" => 'ssl://smtp.gmail.com',
"mail_smtpport" => 465,
"mail_smtpauth" => true,
"mail_smtpname" => 'USERNAME@gmail.com',
"mail_smtppassword" => 'PASSWORD',
);
?>
NOTE: Configure the administrator email from the ownCloud admin panel under the "Settings -> Personal -> Email" menu.

To configure the application to use other third-party SMTP services for outgoing email, such as SendGrid or Mandrill, refer to the FAQ.

NOTE: If you are using Gmail as the outbound email server and have experienced issues trying to send emails correctly, check the How to troubleshoot Gmail SMTP issues to learn the causes of these issues and how to solve them.

How to create a full backup of ownCloud?

The Bitnami ownCloud Stack is self-contained and the simplest option for performing a backup is to copy or compress the Bitnami stack installation directory. To do so in a safe manner, you will need to stop all servers, so this method may not be appropriate if you have people accessing the application continuously.

NOTE: If you want to create only a database backup, refer to these instructions for MySQL and PostgreSQL.

Backup on Linux and Mac OS X

Follow these steps:

  • Change to the directory in which you wish to save your backup.

     $ cd /your/directory
    
  • Stop all servers.

     $ sudo installdir/ctlscript.sh stop
    
  • Create a compressed file with the stack contents.

     $ sudo tar -pczvf application-backup.tar.gz installdir
    
  • Start all servers.

     $ sudo installdir/ctlscript.sh start
    
  • Download or transfer the application-backup.tar.gz file to a safe location.

You should now download or transfer the application-backup.tar.gz file to a safe location.

Backup on Windows

Follow these steps:

  • Stop all servers using the shortcuts in the Start Menu or the graphical manager tool.

  • Create a compressed file with the stack contents. You can use a graphical tool like 7-Zip or WinZip or just right-click the folder, click "Send to", and select the "Compressed (zipped) folder" option.

  • Download or transfer the compressed file to a safe location.

  • Start all servers using the shortcuts in the Start Menu or the graphical manager tool.

Restore on Linux and Mac OS X

Follow these steps:

  • Change to the directory containing your backup:

    $ cd /your/directory
    
  • Stop all servers.

    $ sudo installdir/ctlscript.sh stop
    
  • Move the current stack to a different location:

    $ sudo mv installdir /tmp/bitnami-backup
    
  • Uncompress the backup file to the original directory:

    $ sudo tar -pxzvf application-backup.tar.gz -C /
    
  • Start all servers.

    $ sudo installdir/ctlscript.sh start
    
IMPORTANT: When restoring, remember to maintain the original permissions for the files and folders. For example, if you originally installed the stack as the root user on Linux, make sure that the restored files are owned by root as well.

Restore on Windows

  • Change to the directory containing your backup:

       $ cd /your/directory
    
  • Stop all servers using the shortcuts in the Start Menu or the graphical manager tool.

  • Uninstall the previous services by executing the following command:

        $ serviceinstall.bat
    
  • Create a safe folder named Backups in the desktop and move the current stack to it. Remember to replace PATH with the right location of your folder:

        $ move installdir \PATH\Backups
    
  • Uncompress the backup file using a tool like 7-Zip or Winzip or just double-click the .zip file to uncompress it, and move it to the original directory.
  • Install services by running the following commands from an elevated command prompt:

      $ cd installdir
      $ serviceinstall.bat INSTALL
    
  • Start all servers using the shortcuts in the Start Menu or the graphical manager tool.

How to upgrade the Bitnami ownCloud Stack?

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.

  • Create a directory to save all the data you need to backup. You can use the commands below (on Linux and Mac OS X):

    $ mkdir ~/owncloud-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 (on Linux and Mac OS X):

    $ sudo cp -rf installdir/apps/owncloud/data ~/owncloud-backup
    $ sudo cp -rf installdir/apps/owncloud/conf/ ~/owncloud-backup
    $ sudo cp installdir/apps/owncloud/htdocs/config ~/owncloud-backup
    
  • Uninstall the previous Bitnami ownCloud Stack.
  • Download the latest version of the Bitnami ownCloud Stack and install it.
  • Restore the 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 installdir/apps/owncloud/htdocs/config/config.php file. To do so, use an editor to modify it manually or the commands below (on Linux and Mac OS X):

    $ sudo cat installdir/apps/owncloud/htdocs/config/config.php | grep -oP "(?<='dbpassword' => )('.*')" | xargs -I % sed -e "s/'dbpassword' => '.*'/'dbpassword' => '%'/g" -i ~/owncloud-backup/config/config.php
    
  • Restore the backup files in the new Bitnami ownCloud Stack. You can use the commands below (on Linux and Mac OS X):

    $ sudo cp -rf ~/owncloud-backup/data installdir/apps/owncloud/data
    $ sudo cp -rf ~/owncloud-backup/config installdir/apps/owncloud/htdocs/
    
  • Restore the permissions (only on Linux and Mac OS X if the stack was installed as root).

    $ sudo chown -R daemon:daemon installdir/apps/owncloud/data/
    $ sudo chown -R daemon:daemon installdir/apps/owncloud/htdocs/config/
    $ sudo chmod 664 installdir/apps/owncloud/htdocs/config/config.php
    
  • Restore the Apache configuration files in the new ownCloud stack. Use the command below:

     $ sudo cp -rf ~/owncloud-backup/conf/ installdir/apps/owncloud/conf/
    
  • Restart Apache using the graphical manager or the command line script:

     $ sudo installdir/ctlscript.sh restart apache
    

That's it! You updated the whole stack!

Upgrade only ownCloud in the Bitnami ownCloud Stack (Admin Panel)

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 owner of the files in your installation:

     $ sudo chown -R daemon installdir/apps/owncloud/htdocs/
     $ sudo chmod 644 installdir/apps/owncloud/htdocs/.user.ini
    
  • Run the upgrade process from the admin panel by navigating to "Settings -> General -> Updater -> Open Updater" and running the upgrade process.

  • If the upgrade works well, restore the permissions of your folder.

     $ sudo chown -R bitnami installdir/apps/owncloud/htdocs/
     $ sudo chmod 444 installdir/apps/owncloud/htdocs/.user.ini
     $ sudo chown -R daemon installdir/apps/owncloud/htdocs/config installdir/apps/owncloud/htdocs/apps
    

That's it! You updated the application! You can find more information about the Upgrade process at the ownCloud official documentation.

Upgrade only ownCloud in the Bitnami ownCloud Stack (Manually)

  • Set the Maintenance Mode:

     $ sudo -u daemon installdir/bin/php installdir/apps/owncloud/htdocs/occ maintenance:mode --on
     $ sudo installdir/ctlscript.sh stop apache
    
  • 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 (on Linux and Mac OS X):

     $ wget https://download.owncloud.org/community/owncloud-10.0.2.tar.bz2
     $ tar xjf owncloud-10.0.2.tar.bz2
    
  • Backup the current installation and substitute it with the new one:

     $ sudo mv installdir/apps/owncloud/htdocs/ installdir/apps/owncloud/htdocs-backup
     $ sudo mv owncloud installdir/apps/owncloud/htdocs/
     $ sudo mv installdir/apps/owncloud/htdocs-backup/config/config.php installdir/apps/owncloud/htdocs/config/
    
  • Restore the permissions (only on Linux and Mac OS X if the stack was installed as root):

     $ sudo chown -R daemon:daemon installdir/apps/owncloud/htdocs/
    
  • Run the upgrade command (this could take a few minutes) and unset the Maintenance mode:

     $ sudo -u daemon /opt/bitnami/php/bin/php installdir/apps/owncloud/htdocs/occ upgrade
     $ sudo -u daemon /opt/bitnami/php/bin/php installdir/apps/owncloud/htdocs/occ occ maintenance:mode --off
    
  • Restore the strong permissions configuration (only on Linux and Mac OS X if the stack was installed as root):

     $ sudo find installdir/apps/owncloud/htdocs/ -type d -exec chmod 0750 {} \;
     $ sudo find installdir/apps/owncloud/htdocs/ -type f -exec chmod 0640 {} \;
     $ sudo chown -R bitnami:daemon installdir/apps/owncloud/htdocs/
     $ sudo chown -R daemon:daemon installdir/apps/owncloud/htdocs/apps
     $ sudo chown -R daemon:daemon installdir/apps/owncloud/htdocs/assets
     $ sudo chown -R daemon:daemon installdir/apps/owncloud/htdocs/config
     $ sudo chown -R daemon:daemon installdir/apps/owncloud/htdocs/themes
    
  • Restart Apache using the graphical manager or the command line script:

     $ sudo installdir/ctlscript.sh restart apache
    

That's it! You updated the application! You can find more information about the Upgrade process at the ownCloud official documentation.

Troubleshooting I: Upgrade ownCloud and all stack components from 4.0.x to 4.5.x

  • Follow the same steps described at Upgrade ownCloud and all stack components section.
  • After restoring the database. Access the new phpMyAdmin installation and log in. Please check our FAQ for instructions on how to connect to phpMyAdmin.
  • Select the bitnami_owncloud database and execute the following SQL commands to create the tables that they are not present in the previous version:

     CREATE TABLE IF NOT EXISTS `oc_queuedtasks` (
     `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
     `app` varchar(255) NOT NULL DEFAULT '',
     `klass` varchar(255) NOT NULL DEFAULT '',
     `method` varchar(255) NOT NULL DEFAULT '',
     `parameters` varchar(255) NOT NULL DEFAULT '',
     PRIMARY KEY (`id`)
     ) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;
    
     CREATE TABLE IF NOT EXISTS `oc_group_admin` (
     `gid` varchar(64) NOT NULL DEFAULT '',
     `uid` varchar(64) NOT NULL DEFAULT ''
     ) ENGINE=MyISAM DEFAULT CHARSET=utf8;
    
     CREATE TABLE IF NOT EXISTS `oc_share` (
     `id` int(11) NOT NULL AUTO_INCREMENT,
     `share_type` tinyint(4) NOT NULL DEFAULT '0',
     `share_with` varchar(255) DEFAULT NULL,
     `uid_owner` varchar(255) NOT NULL DEFAULT '',
     `parent` int(11) DEFAULT NULL,
     `item_type` varchar(64) NOT NULL DEFAULT '',
     `item_source` varchar(255) DEFAULT NULL,
     `item_target` varchar(255) DEFAULT NULL,
     `file_source` int(11) DEFAULT NULL,
     `file_target` varchar(512) DEFAULT NULL,
     `permissions` tinyint(4) NOT NULL DEFAULT '0',
     `stime` bigint(20) NOT NULL DEFAULT '0',
     `accepted` tinyint(4) NOT NULL DEFAULT '0',
     `expiration` timestamp DEFAULT CURRENT_TIMESTAMP,
     PRIMARY KEY (`id`)
     ) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;
    
  • Follow the rest of the steps.

Troubleshooting II: Upgrade ownCloud and all stack components from 6.0.x to 7.0.x

How to create an SSL certificate?

OpenSSL is required to create an SSL certificate. A certificate request can then be sent to a certificate authority (CA) to get it signed into a certificate, or if you have your own certificate authority, you may sign it yourself, or you can use a self-signed certificate (because you just want a test certificate or because you are setting up your own CA).

Follow the steps below for your platform.

Linux and Mac OS X

NOTE: OpenSSL will typically already be installed on Linux and Mac OS X. If not installed, install it manually using your operating system's package manager.

Follow the steps below:

  • Generate a new private key:

     $ sudo openssl genrsa -out installdir/apache2/conf/server.key 2048
    
  • Create a certificate:

     $ sudo openssl req -new -key installdir/apache2/conf/server.key -out installdir/apache2/conf/cert.csr
    
    IMPORTANT: Enter the server domain name when the above command asks for the "Common Name".
  • Send cert.csr to the certificate authority. When the certificate authority completes their checks (and probably received payment from you), they will hand over your new certificate to you.

  • Until the certificate is received, create a temporary self-signed certificate:

     $ sudo openssl x509 -in installdir/apache2/conf/cert.csr -out installdir/apache2/conf/server.crt -req -signkey installdir/apache2/conf/server.key -days 365
    
  • Back up your private key in a safe location after generating a password-protected version as follows:

     $ sudo openssl rsa -des3 -in installdir/apache2/conf/server.key -out privkey.pem
    

    Note that if you use this encrypted key in the Apache configuration file, it will be necessary to enter the password manually every time Apache starts. Regenerate the key without password protection from this file as follows:

     $ sudo openssl rsa -in privkey.pem -out installdir/apache2/conf/server.key
    

Windows

NOTE: OpenSSL is not typically installed on Windows. Before following the steps below, download and install a binary distribution of OpenSSL.

Follow the steps below once OpenSSL is installed:

  • Set the OPENSSL_CONF environment variable to the location of your OpenSSL configuration file. Typically, this file is located in the bin/ subdirectory of your OpenSSL installation directory. Replace the OPENSSL-DIRECTORY placeholder in the command below with the correct location.

     $ set OPENSSL_CONF=C:\OPENSSL-DIRECTORY\bin\openssl.cfg
    
  • Change to the bin/ sub-directory of the OpenSSL installation directory. Replace the OPENSSL-DIRECTORY placeholder in the command below with the correct location.

     $ cd C:\OPENSSL-DIRECTORY\bin
    
  • Generate a new private key:

     $ openssl genrsa -out installdir/apache2/conf/server.key 2048
    
  • Create a certificate:

     $ openssl req -new -key installdir/apache2/conf/server.key -out installdir/apache2/conf/cert.csr
    
    IMPORTANT: Enter the server domain name when the above command asks for the "Common Name".
  • Send cert.csr to the certificate authority. When the certificate authority completes their checks (and probably received payment from you), they will hand over your new certificate to you.

  • Until the certificate is received, create a temporary self-signed certificate:

     $ openssl x509 -in installdir/apache2/conf/cert.csr -out installdir/apache2/conf/server.crt -req -signkey installdir/apache2/conf/server.key -days 365
    
  • Back up your private key in a safe location after generating a password-protected version as follows:

     $ openssl rsa -des3 -in installdir/apache2/conf/server.key -out privkey.pem
    

    Note that if you use this encrypted key in the Apache configuration file, it will be necessary to enter the password manually every time Apache starts. Regenerate the key without password protection from this file as follows:

     $ openssl rsa -in privkey.pem -out installdir/apache2/conf/server.key
    

Find more information about certificates at http://www.openssl.org.

How to enable HTTPS support with SSL certificates?

TIP: If you wish to use a Let's Encrypt certificate, you will find specific instructions for enabling HTTPS support with Let's Encrypt SSL certificates in our Let's Encrypt guide.
NOTE: The steps below assume that you are using a custom domain name and that you have already configured the custom domain name to point to your cloud server.

Bitnami images come with SSL support already pre-configured and with a dummy certificate in place. Although this dummy certificate is fine for testing and development purposes, you will usually want to use a valid SSL certificate for production use. You can either generate this on your own (explained here) or you can purchase one from a commercial certificate authority.

Once you obtain the certificate and certificate key files, you will need to update your server to use them. Follow these steps to activate SSL support:

  • Use the table below to identify the correct locations for your certificate and configuration files.

    Variable Value
    Current application URL https://[custom-domain]/
      Example: https://my-domain.com/ or https://my-domain.com/appname
    Apache configuration file installdir/apache2/conf/bitnami/bitnami.conf
    Certificate file installdir/apache2/conf/server.crt
    Certificate key file installdir/apache2/conf/server.key
    CA certificate bundle file (if present) installdir/apache2/conf/server-ca.crt
  • Copy your SSL certificate and certificate key file to the specified locations.

    NOTE: If you use different names for your certificate and key files, you should reconfigure the SSLCertificateFile and SSLCertificateKeyFile directives in the corresponding Apache configuration file to reflect the correct file names.
  • If your certificate authority has also provided you with a PEM-encoded Certificate Authority (CA) bundle, you must copy it to the correct location in the previous table. Then, modify the Apache configuration file to include the following line below the SSLCertificateKeyFile directive. Choose the correct directive based on your scenario and Apache version:

    Variable Value
    Apache configuration file installdir/apache2/conf/bitnami/bitnami.conf
    Directive to include (Apache v2.4.8+) SSLCACertificateFile "installdir/apache2/conf/server-ca.crt"
    Directive to include (Apache < v2.4.8) SSLCertificateChainFile "installdir/apache2/conf/server-ca.crt"
    NOTE: If you use a different name for your CA certificate bundle, you should reconfigure the SSLCertificateChainFile or SSLCACertificateFile directives in the corresponding Apache configuration file to reflect the correct file name.
  • Once you have copied all the server certificate files, you may make them readable by the root user only with the following commands:

     $ sudo chown root:root installdir/apache2/conf/server*
    
     $ sudo chmod 600 installdir/apache2/conf/server*
    
  • Open port 443 in the server firewall. Refer to the FAQ for more information.

  • Restart the Apache server.

You should now be able to access your application using an HTTPS URL.

How to force HTTPS redirection with Apache?

Add the following lines in the default Apache virtual host configuration file at installdir/apache2/conf/bitnami/bitnami.conf, inside the default VirtualHost directive, so that it looks like this:

<VirtualHost _default_:80>
  DocumentRoot "installdir/apache2/htdocs"
  RewriteEngine On
  RewriteCond %{HTTPS} !=on
  RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [R,L]
  ...
</VirtualHost>

After modifying the Apache configuration files:

  • Open port 443 in the server firewall. Refer to the FAQ for more information.

  • Restart Apache to apply the changes.

How to debug Apache errors?

Once Apache starts, it will create two log files at installdir/apache2/logs/access_log and installdir/apache2/logs/error_log respectively.

  • The access_log file is used to track client requests. When a client requests a document from the server, Apache records several parameters associated with the request in this file, such as: the IP address of the client, the document requested, the HTTP status code, and the current time.

  • The error_log file is used to record important events. This file includes error messages, startup messages, and any other significant events in the life cycle of the server. This is the first place to look when you run into a problem when using Apache.

If no error is found, you will see a message similar to:

Syntax OK

Updating the IP address or hostname

ownCloud requires updating the IP address/domain name if the machine IP address/domain name changes. The bnconfig tool also has an option which updates the IP address, called --machine_hostname (use --help to check if that option is available for your application). Note that this tool changes the URL to http://NEW_DOMAIN/owncloud.

$ sudo installdir/apps/owncloud/bnconfig --machine_hostname NEW_DOMAIN

If you have configured your machine to use a static domain name or IP address, you should rename or remove the installdir/apps/owncloud/bnconfig file.

$ sudo mv installdir/apps/owncloud/bnconfig installdir/apps/owncloud/bnconfig.disabled
NOTE: Be sure that your domain is propagated. Otherwise, this will not work. You can verify the new DNS record by using the Global DNS Propagation Checker and entering your domain name into the search field.

You can also change your hostname by modifying it in your hosts file. Enter the new hostname using your preferred editor.

$ sudo nano /etc/hosts
  • Add a new line with the IP address and the new hostname. Here's an example. Remember to replace the IP-ADDRESS and DOMAIN placeholders with the correct IP address and domain name.

    IP-ADDRESS DOMAIN

How to find the MySQL database credentials?

How to connect to the MySQL database?

You can connect to the MySQL database from the same computer where it is installed with the mysql client tool.

$ mysql -u root -p

You will be prompted to enter the root user password. This is the same as the application password.

How to debug errors in your database?

The main log file is created at installdir/mysql/data/mysqld.log on the MySQL database server host.

How to change the MySQL root password?

You can modify the MySQL password using the following command at the shell prompt. Replace the NEW_PASSWORD placeholder with the actual password you wish to set.

$ installdir/mysql/bin/mysqladmin -p -u root password NEW_PASSWORD

How to reset the MySQL root password?

If you don't remember your MySQL root password, you can follow the steps below to reset it to a new value:

  • Create a file in /home/bitnami/mysql-init with the content shown below (replace NEW_PASSWORD with the password you wish to use):

     UPDATE mysql.user SET Password=PASSWORD('NEW_PASSWORD') WHERE User='root';
     FLUSH PRIVILEGES;
    

    If your stack ships MySQL v5.7.x, use the following content instead of that shown above:

     UPDATE mysql.user SET authentication_string=PASSWORD('NEW_PASSWORD') WHERE User='root';
     FLUSH PRIVILEGES;
    
    TIP: Check the MySQL version with the command installdir/mysql/bin/mysqladmin --version or installdir/mysql/bin/mysqld --version.
  • Stop the MySQL server:

     $ sudo installdir/ctlscript.sh stop mysql
    
  • Start MySQL with the following command:

     $ sudo installdir/mysql/bin/mysqld_safe --pid-file=installdir/mysql/data/mysqld.pid --datadir=installdir/mysql/data --init-file=/home/bitnami/mysql-init 2> /dev/null &
    
  • Restart the MySQL server:

     $ sudo installdir/ctlscript.sh restart mysql
    
  • Remove the script:

     $ rm /home/bitnami/mysql-init
    

How to change the MySQL root password in Windows?

You can modify the MySQL password using the following command at the shell prompt. Replace the NEW_PASSWORD placeholder with the actual password you wish to set.

installdir\mysql\bin\mysqladmin.exe -p -u root password NEW_PASSWORD

How to reset the MySQL root password in Windows?

If you don't remember your MySQL root password, you can follow the steps below to reset it to a new value:

  • Stop the MySQL server using the graphic manager tool. Refer to the how to start or stop the services section.
  • Check the MySQL version:

    installdir\mysql\bin\mysqladmin.exe –version

  • Create a file named mysql-init.txt with the content shown below depending on your MySQL version (replace NEW_PASSWORD with the password you wish to use):
    • MySQL 5.6.x or earlier:

       UPDATE mysql.user SET Password=PASSWORD('NEW_PASSWORD') 
       WHERE User='root';
       FLUSH PRIVILEGES;
      
    • MySQL 5.7.x or later:

       ALTER USER 'root'@'localhost' IDENTIFIED BY 'NEW_PASSWORD'; 
      
  • Start MySQL server with the following command. Remember to replace PATH with the location in which you have saved the mysql-init.txt file:

     installdir " installdir\mysql\bin\mysqld.exe" --defaults-file=" installdir\mysql\my.ini" --init-file="\PATH\mysql-init.txt" --console
    
    • The --init file option is used by the server for executing the content of the mysql-init.txt file at startup, it will change each root account password.
    • The --defaults-file option is specified since you have installed MySQL using the Bitnami installer.
    • The --console option (optional) has been added in order to show the server output at the console window rather than in the log file.
  • After some minutes, hit Ctrl-C to force the shutdown.
  • Restart the MySQL server from the graphic manager tool.
  • After the server has restarted successfully, delete the mysql-init.txt file.

How to access phpMyAdmin?

You should be able to access phpMyAdmin directly, by browsing to http://127.0.0.1/phpmyadmin.

The username is root for phpMyAdmin, and the password is the one specified by you during the installation process.

How to modify PHP settings for Apache?

The PHP configuration file allows you to configure the modules enabled, the email settings or the size of the upload files. It is located at installdir/php/etc/php.ini.

For example, to modify the default upload limit for PHP, update the PHP configuration file following these instructions.

After modifying the PHP configuration file, restart both Apache and PHP-FPM for the changes to take effect:

$ sudo installdir/ctlscript.sh restart apache
$ sudo installdir/ctlscript.sh restart php-fpm

How to modify the allowed limit for uploaded files in Apache?

Modify the following options in the installdir/php/etc/php.ini file to increase the allowed size for uploads:

; Maximum size of POST data that PHP will accept.
post_max_size = 16M

; Maximum allowed size for uploaded files.
upload_max_filesize = 16M

Restart PHP-FPM and Apache for the changes to take effect.

$ sudo installdir/ctlscript.sh restart apache
$ sudo installdir/ctlscript.sh restart php-fpm    

How to enforce ownCloud security?

ownCloud provides several tips to improve application performance when you access the admin panel.

* No memory cache has been configured. To enhance your performance please configure a memcache if available. Further information can be found in our documentation.

ownCloud recommends configuring caching. It improves performance by storing data, code, and other objects in memory. [Find out more](https://doc.owncloud.org/server/8.1/admin_manual/configuration_server/performance_tuning.html).

*

    You are accessing this site via HTTP. We strongly suggest you configure your server to require using HTTPS instead as described in our security tips.

ownCloud also suggests access using HTTPS instead of HTTP. [Find out more](/installer/components/apache).

* The "Strict-Transport-Security" HTTP header is not configured to least "15768000" seconds. For enhanced security we recommend enabling HSTS as described in our security tips.

To follow this suggestion, add the line below in the *installdir/apps/owncloud/conf/httpd-app.conf* file:

     Header always add Strict-Transport-Security "max-age=15768000; includeSubDomains; preload"

How to configure the ownCloud desktop client?

ownCloud makes client apps available for Windows, OS X, and Linux desktops, and for Android and iOS devices. Desktop clients are available from the ownCloud Web site. The apps for mobile devices are available on Google Play and the Apple App Store.

Once you have installed the desktop client for your operating system, follow these steps to configure it to sync with your ownCloud server:

  • Launch the ownCloud desktop client.

  • In the connection wizard, enter the IP address for your server. If you did not set up HTTPS support on your server, ensure you are using http:// and not https://. Click "Next" to proceed.

    ownCloud client configuration

  • Enter your username and password and click "Next".

    ownCoud client configuration

  • Specify whether to sync everything or only selected files. Also, specify a location for the local files to reside.

    ownCloud client configuration

  • Click "Connect" and then "Finish" to save the settings.

How to configure cron jobs?

ownCloud allows three methods for executing background jobs, as described in the ownCloud manual. By default, the AJAX mode is configured to run scheduled tasks.

If you prefer to use cron, edit the crontab by running the following command

$ sudo crontab -e

Add the following line at the end of the file:

*/15 * * * *  su daemon -s /bin/sh -c "installdir/php/bin/php -f installdir/apps/owncloud/htdocs/cron.php > /dev/null 2>&1"

Note that the cron job will be executed by the user account used to install the stack.

How to configure fail2ban to work with ownCloud?

If you want to limit the number of login attempts (and avoid brute-force attacks), install fail2ban and configure it to work with the Bitnami ownCloud Stack.

  • Install fail2ban:

    • Debian:

      $ sudo apt-get update
      $ sudo apt-get install fail2ban
      
    • CentOS:

      $ sudo yum install epel-release
      $ sudo yum install fail2ban
      $ sudo systemctl enable fail2ban
      $ sudo systemctl start fail2ban
      
  • Log in to ownCloud, click your username in the top right corner, navigate to the "Admin -> Log" section and choose "warnings, errors and fatal issues".

    [![ownCloud logger](/images/img/apps/owncloud/owncloud-logger-d7a0717e.png){: .img-medium}](/images/img/apps/owncloud/owncloud-logger-d7a0717e.png)
    

Next, configure fail2ban following the steps below:

  • Create the /etc/fail2ban/filter.d/owncloud.conf file with the following code:

      [Definition]
      failregex={"reqId":".*","remoteAddr":".*","app":"core","message":"Login failed: '.*' \(Remote IP: '<HOST>\)","level":2,"time":".*"}
      ignoreregex =
    
  • Copy the /etc/fail2ban/jail.conf file to the /etc/fail2ban/jail.local file and add the code below:

      #OwnCloud
      [owncloud]
      enabled  = true
      filter   = owncloud
      action = iptables-multiport[name=owncloud, port="http,https"]
      logpath  = installdir/apps/owncloud/data/owncloud.log
      maxretry = 5
      findtime = 600
      bantime = 600
    

    This fail2ban configuration will ban the IP of any user that tried to access five (maxretry) different times in 10 minutes (findtime) without success. Note that the ban only will affect the ports 80 and 443, and the user with the banned IP will not be able to contact the web server for 10 minutes (bantime).

  • Before applying the configuration,test if the regex configuration is correct. To test this, browse to your Bitnami ownCloud login page and use a non-existent user/password to get a login error. Then, run this command:

      $ sudo fail2ban-regex installdir/apps/owncloud/data/owncloud.log /etc/fail2ban/filter.d/owncloud.conf 
    

    If the last two lines of the output show you at least "1 matched", the regex is properly configured:

      Lines: 412 lines, 0 ignored, 1 matched, 397 missed
      Missed line(s):: too many to print.  Use --print-all-missed to print all 397 lines
    
  • Apply the configuration with this command

    • Debian:

        $ sudo /etc/init.d/fail2ban restart
      
    • CentOS:

        $ sudo systemctl restart fail2ban
      

To check if all is working, try logging in five different times with bad credentials. On the fifth unsuccessful attempt, you will be banned for 10 minutes.

How to fix the WebDav error in the admin panel?

If you see this error in your admin panel,

Your web server is not yet properly setup to allow files synchronization because the WebDAV interface seems to be broken. Please double check the installation guides.

this is because you did not configure your own certificate for your server. Find out how to configure your own SSL certificate.

You can continue using the ownCloud Desktop clients to sync files.

How to modify the allowed limit for uploaded files?

Modify the following options in the installdir/apps/owncloud/conf/php-fpm/php-settings.conf file to increase the allowed size for uploads:

; Maximum size of POST data that PHP will accept.
php_value[post_max_size]=4000M

; Maximum allowed size for uploaded files.
php_value[upload_max_filesize]=4000M

Restart PHP-FPM and Apache for the changes to take effect.

$ sudo installdir/ctlscript.sh restart apache
$ sudo installdir/ctlscript.sh restart php-fpm

How to migrate to a newer version of ownCloud Server?

If you wish to quickly migrate to the latest version of ownCloud Server, you can use the ownCloud desktop client to simplify the process, by deploying a new version of the Bitnami ownCloud Stack and using the desktop client to transfer data to it.

NOTE: This approach does not represent a complete upgrade or migration, as it does not migrate the user's account or the configuration data in ownCloud Server. It is best suited for users who only wish to sync their files and other data.

Follow these steps:

  • Launch the ownCloud desktop client and let it sync with the existing ownCloud Server. This step ensures that all data on the server is copied to the local ownCloud storage area.
TIP: If this is the first time you are using the ownCloud desktop client, download it from the ownCloud Web site and configure it as described in these instructions.
  • Once the synchronization process is complete, use the "Account -> Remove" menu option and then click the "Remove connection" button to remove the connection to the existing ownCloud server.

    ownCloud client configuration

  • Close the ownCloud desktop client.

  • Deploy a new server with the latest version of the Bitnami ownCloud Stack.

  • Log in to the new ownCloud Server using your Web browser.

  • In the left navigation bar, select the "All files" option. Then, select all the files and folders shown and delete them.

    ownCloud server configuration

  • Launch the ownCloud desktop client again.

  • Create a connection to the new ownCloud Server following these instructions.

  • When asked to configure local folder options, ensure that the "Sync everything from server" and "Keep local data" options are selected.

    ownCloud client configuration

  • Click "Connect" and then "Finish" to save the settings.

The ownCloud desktop client will now connect to the new ownCloud Server and synchronize the files that are already in local storage with the new server. At the end of the synchronization process, the new ownCloud Server will have the same data as the original ownCloud Server. You can now decommission the old ownCloud Server and use the new one instead.

How to modify the ownCloud trusted domains?

If you only have one domain configured to access your ownCloud installation, you can configure it using the bnconfig tool

$ installdir/apps/owncloud/bnconfig --machine_hostname DOMAIN

If you have one or more domains to access your ownCloud installation, you can add them manually in the installdir/apps/owncloud/htdocs/config/config.php file:

'trusted_domains' =>
array (
    0 => "FIRST_DOMAIN",
    1 => "SECOND_DOMAIN",
    2 => "THIRD_DOMAIN",
),

How to test the ownCloud desktop client?

First, ensure that the ownCloud desktop client is correctly configured. Then, follow these steps:

  • Open a document creator such as a word processor or text editor.

  • Type some content in the document, and then save it to the local directory that was specified during configuration of the ownCloud desktop client.

  • Wait a moment and then click the "Sync Protocol" tab. Sync messages for that file and others appear.

    ownCoud client validation

  • Open a web browser and log into your ownCloud interface.

  • Click the "Documents" folder, and verify that your file was uploaded.

    ownCoud client validation

  • Click the home icon in the breadcrumbs above the list of files.

  • Click the "Photos" folder and the upload icon. In the resulting pop-up menu, click "Upload".

    ownCoud client validation

  • Select an image file and click "Open".

  • Confirm that the photo uploaded using the browser-based interface.

    ownCoud client validation

  • Switch to the desktop client. Confirm that the file you uploaded to the web interface appears in the "Activity" tab.

    ownCoud client validation

You've now validated the installation of the desktop client.

How to connect with other ownCloud servers?

ownCloud supports "federated sharing", which essentially means connecting an ownCloud server with other ownCloud servers to enable sharing between them. Federated sharing is enabled by default in ownCloud 9 and better.

NOTE: Federated sharing requires all involved ownCloud servers to be public, so that they can communicate with each other.

To use this feature, ensure that you have a running ownCloud server and the details of another ownCloud server you wish to connect to, and then follow the steps below:

  • Log in to your ownCloud server.

  • Use the "Files -> All files" menu item to find the file you wish to share. Click the "Share" icon next to the filename.

    ownCloud file sharing

  • In the "Sharing" side panel, tick the "Share link" checkbox and copy the resulting URL. Send this URL to the user you wish to share the file with.

    ownCloud file sharing

The recipient of the URL must perform the following steps:

  • Browse to the share URL.

  • On the resulting page, click the "Add to your ownCloud" button and enter the URL of the destination ownCloud server (the server the file should be shared with).

    ownCloud file sharing

The source ownCloud server will attempt to connect to the destination ownCloud server and share the selected file. The recipient may need to log in to the destination ownCloud server and confirm the share operation as part of the process.

ownCloud file sharing

If successful, the remote user will be able to see the shared file under the "Files -> Shared with you" menu item on the remote ownCloud server.

ownCloud file sharing

The share can be undone at any time by unchecking the "Share link" checkbox under the file's "Sharing" side panel on the source ownCloud server.

How to integrate ownCloud and LibreOffice?

NOTE: ownCloud requires LibreOffice 4.2 or better.

To use ownCloud with LibreOffice, LibreOffice and Java should be installed on your system. To install LibreOffice, download it from the LibreOffice website and follow the installation steps. Note the installation path.

To allow ownCloud to use LibreOffice for editing OpenDocument and Microsoft Word files, follow these steps:

  • Add the path to the LibreOffice binary file in the ownCloud configuration file at installdir/apps/owncloud/htdocs/config/config.php, just before the end:

     'preview_libreoffice_path' => 'path_to_your_libreoffice_binary'
    
  • Access your ownCloud dashboard, go to the administration panel, and click "Apply and Test" in the "Documents" section. In case you see an error like the one below, please try again, as the configuration is typically applied properly on the second attempt.

    ownCloud and LibreOffice

    ownCloud and LibreOffice

If all went well, it should now be possible to edit OpenDocument and Microsoft Word files through the "Documents" application.

nativeInstaller

Bitnami Documentation