BitNami ownCloud

    ownCloud is a flexible, open source file sync and share solution. Whether using a mobile device, a workstation, or a web client, ownCloud provides the ability to put the right files at their employees’ fingertips on any device in one simple-to-use, secure, private and controlled solution.

    Please, take a look to the Quick Start Guide to know the basic use of this Stack.

    How to start/stop the servers?

    Graphical tool

    The Stacks include a graphical tool to manage the servers easily. You can find the "manager-windows.exe", "manager-osx" or "manager-linux" tool in your installation directory. Using this tool, you can Start, Stop or Restart the servers and check the log files. You can click on the icon to start it.

    manager-servers.png

     

    manager-osx.png

     

     

     

     

     

     

     

     

     


    win_platform.png

    On Windows: You can also start the Manager tool from shortcuts: Start -> Program Files -> BitNami Stack -> Manager tool

    Command line tool

    If you prefer, you can use the "ctlscript.sh" utility from the command line. This script is in the installation directory.

    linux_platform.png

    On Virtual Machines and Cloud images:

    $ sudo /opt/bitnami/ctlscript.sh start

    A native installer on Linux:

    $ cd ~/application-version
    $ ./ctlscript.sh start
    

    mac_platform.png

     

    On OS X: You can start the Manager tool from the installation directory or you can use the "ctlscript.sh" utility from a Terminal.

    host:~ user$ cd /Applications/application-version
    host:~ user$ ./ctlscript.sh start

    How to change the default URL?

    This approach describes how to configure your application to run in the root URL directly. Also, you will be able to modify the URL to a NEW_DOMAIN using the bnconfig tool. The details are described below.

    Automatic Approach

    This approach is based on the Bitnami Configuration Tool (bnconfig).

    Bitnami Cloud Hosting

    The best way to change your URL in BCH is to go to your application tab and modify it there. In the Bitnami Cloud Hosting console, select Servers, choose your server, Manage and go to the Applications tab. Press there the pencil next to the application which URL you want to modify and choose .

    Cloud Images and Virtual Machines

    Moving the application to /

     If your application is running in "/owncloud" you can remove the prefix from the URL executing the following command:

    $ sudo /opt/bitnami/apps/owncloud/bnconfig --appurl /
    

    (use --help to check if that option is available for your application)

    Now you will be able to access to the application at http://YOUR_DOMAIN instead of http://YOUR_DOMAIN/owncloud.

    Updating the IP or hostname

    Some applications require to update the IP/domain if the machine IP/domain changes. The bnconfig tool also has an option which updates the IP automatically during boot, 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 /opt/bitnami/apps/owncloud/bnconfig --machine_hostname NEW_DOMAIN
    

    If you already moved your application to the root URL you should include both options at the same time.

    sudo /opt/bitnami/apps/owncloud/bnconfig --appurl / --machine_hostname NEW_DOMAIN

     

    If you have configured your machine to use an static domain name or IP, you should rename or remove the "/opt/bitnami/apps/owncloud/bnconfig" file.

    sudo mv /opt/bitnami/apps/owncloud/bnconfig /opt/bitnami/apps/owncloud/bnconfig.disabled

     

    Native Installer

    Remember to use your actual installation directory instead of installdir.

    Moving the application to /

    If your application is running in "/owncloud" you can remove the prefix from the URL executing the following command:

    On Linux,

    installdir/apps/owncloud/bnconfig --appurl /
    

    On Mac OS X, 

    installdir/apps/owncloud/bnconfig.app/Contents/MacOS/installbuilder.sh --appurl /
    

    On Windows,

    installdir/apps/owncloud/bnconfig.exe --appurl /
    

    (use --help to check if that option is available for your application)

    Now you will be able to access to the application at http://YOUR_DOMAIN instead of http://YOUR_DOMAIN/owncloud.

    Updating the IP or hostname

    Some applications require to update the IP/domain if the machine IP/domain changes. The bnconfig tool also has an option which updates the IP automatically during boot, 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.

    installdir/apps/owncloud/bnconfig --machine_hostname NEW_DOMAIN
    

    If you already moved your application to the root URL you should include both options at the same time.

    installdir/apps/owncloud/bnconfig --appurl / --machine_hostname NEW_DOMAIN
    

     

    If you have configured your machine to use an static domain name or IP, you should rename or remove the "/opt/bitnami/apps/owncloud/bnconfig" file.

    mv installdir/apps/owncloud/bnconfig installdir/apps/owncloud/bnconfig.disabled
    

    Tabs end

    Manual Approach

    If you want to change the default URL from http://your_domain/owncloud to http://your_domain, you should add a "DocumentRoot" entry in your application conf file. Edit the installdir/apps/owncloud/conf/httpd-prefix.conf file to add this line and commenting the "Alias" entries. Modify the

    httpd_prefix.conf file content (substitute installdir with your actual installation directory, which is /opt/bitnami in Cloud Images and Virtual Machines):

    DocumentRoot "/installdir/apps/owncloud/htdocs"
    # Alias /owncloud/ "/installdir/apps/owncloud/htdocs/"
    # Alias /owncloud "/installdir/apps/owncloud/htdocs"
    
    (...)
    

    Some applications also require changes in their configuration files or in the database.
     

    How to create a full backup of ownCloud?

    Because BitNami stacks are self-contained, the simplest option for performing your backups 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 continously.

    linux_platform.pngOn Virtual Machines and Cloud Images:

    sudo /opt/bitnami/ctlscript.sh stop

    mac_platform.png

    On OS X:

    $ cd installdir
    $ ./ctlscript.sh stop
    $ cp -r installdir application-backup
    

    Or you can create a tarball:

    $ tar -czvf application-backup.tar.gz installdir
    

    Or a zip file:

    $ zip -r application-backup.zip installdir/*

    To restore this backup you only need to uncompress the backup in the same location. It is important to use the same path that was used when the stack was originally installed.

    For example if you have a backup in a Red Hat machine, you can copy it to an Ubuntu Linux machine (a different distro!) in the same location. Then start the servers and that’s all.

    On Virtual Machines and Cloud Images:

    $ sudo /opt/bitnami/ctlscript.sh start

    On OS X:

    $ cd installdir
    $ ./ctlscript.sh start
    

    You just need to be carefull to keep the same permissions for the files and folders. If you installed as root make sure that in the new machine you copy the files also as root. And this case, if you are also moving MySQL or PostgreSQL, you will need to create those users in the new machine (if they don't exist yet).

    win_platform.png On Windows you should follow the same process. Stop the servers using the shortcuts and copy the whole installation directory. To restore the system, copy the directory to a different Windows machine in the same location and follow these steps from a command prompt:

    $ cd installdir
    $ serviceinstall.bat INSTALL
    

    You can access your BitNami Application at the usual URL.

    If you want to create only a database backup, check the following link for MySQL /Components/MySQL#How_to_create_a_database_backup or for PostgreSQL /Components/PostgreSQL#How_to_create_a_database_backup.3f

    How to fix the WebDav error in the 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.
    

    If you see this error in your admin panel it is because you did not configure your own certificate for your server. You can find more info about how to configure your own SSL certificate here.

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

    How to upgrade ownCloud?

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

    There are two different ways to upgrade your application.

    1. If you want to upgrade the application and all Stack components PHP, Ruby, MySQL, Apache… You can follow the steps described at How to upgrade the full Stack migrating the data?
    2. In case you only want to upgrade the application code without modifying any other Stack components,  you should follow the guide which is in the application page itself.

    Upgrading from the ownCloud admin panel

    ownCloud already have installed the "Updater" app that allows you to upgrade ownCloud application from the admin panel directly. For security reasons, ownCloud files do not have write access for the web server user but that is 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 /opt/bitnami/apps/owncloud/htdocs

    Then run the upgrade process from the admin panel: "Admin" -> "Update center" and run the upgrade process.

    If the upgrade works well, we strongly suggest to restore the permissions of your folder. 

    sudo chown -R bitnami /opt/bitnami/apps/owncloud/htdocs
    sudo chown -R daemon /opt/bitnami/apps/owncloud/htdocs/config /opt/bitnami/apps/owncloud/htdocs/apps

    Then you can access to your new ownCloud application. You can find more info at http://owncloud.org/support/upgrade/

    Full Stack upgrade from ownCloud 4.0.x to ownCloud 4.5.x

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

    1. From ownCloud 4.0.x installation, save the following folders:
      1. /installdir/apps/owncloud/data
      2. /installdir/apps/owncloud/htdocs/config
    2. Export the database using phpMyAdmin (using the user root and the password used in the installation process) on the URL: http://127.0.0.1/phpmyadmin. After log in, select the bitnami_owncloud database, and press in Export button. Export it using the default parameters.
    3. Uninstall the ownCloud 4.0.x installation keeping the full backup done before.
    4. Install the new ownCloud 4.5.x.
    5. After the installation is complete, copy the data folder saved from the 4.0.x installation in the new /installdir/apps/owncloud/data path.
    6. Edit the config/config.php file from the 4.0.x installation and change the 'dbpassword' and 'datadirectory' parameters using the new ones that can be found in the new /installdir/apps/owncloud/htdocs/config/config.php file.
    7. Afterwards, copy the config folder from the 4.0.x installation updated with the new dbpassword parameter in the new /installdir/apps/owncloud/htdocs/config path.
    8. Finally, the database must be imported. To do so,
      1. Access to the new phpMyAdmin and log in. Click on bitnami_owncloud database and remove all tables.
      2. Click on the import button and import your saved file with the default options.
      3. Click on the SQL button 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 ;
    
    1. Restart the apache service and access to your upgraded application.
    Full Stack upgrade from ownCloud 6.0.x to ownCloud 7.0.x

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

    1. From ownCloud 6.0.x installation, save the following folders:
      1. /installdir/apps/owncloud/data
      2. /installdir/apps/owncloud/htdocs/config
    2. Export the database using phpMyAdmin (using the user root and the password used in the installation process) on the URL: http://127.0.0.1/phpmyadmin. After log in, select the bitnami_owncloud database, and press in Export button. Export it using the default parameters.
    3. Uninstall the ownCloud 6.0.x installation keeping the full backup done before.
    4. Install the new ownCloud 7.0.x.
    5. After the installation is complete, copy the data folder saved from the 6.0.x installation in the new /installdir/apps/owncloud/data path.
    6. Edit the config/config.php file from the 6.0.x installation and change the 'dbpassword' and 'datadirectory' parameters using the new ones that can be found in the new /installdir/apps/owncloud/htdocs/config/config.php file. Also modify the 'version' parameter to match the new one.
    7. Afterwards, copy the config folder from the 6.0.x installation updated with the new dbpassword parameter in the new /installdir/apps/owncloud/htdocs/config path.
    8. Finally, the database must be imported. To do so,
      1. Access to the new phpMyAdmin and log in. Click on bitnami_owncloud database and remove all tables.
      2. Click on the import button and import your saved file with the default options.
      3. Click on the SQL button and execute the following SQL commands to create add the permissions column in the filecache table
    ALTER TABLE oc_filecache ADD permissions int(11);
    
    1. Restart the apache service and access to your upgraded application.

    How to configure ownCloud Sync Clients?

    The ownCloud Sync Clients lets you sync one ore more specified directories on the local machine with your ownCloud application. Files on your ownCloud are automatically the same as the ones on the local disk.

    You can download the Client for Windows, OS X or Linux at http://owncloud.org/sync-clients/

    Once you installed on your system, check that you have a cloud icon in your Desktop dock. Click on it and go to "Settings". You have to set hte IP address of the machine where you installed Bitnami ownCloud stack. Note that you have to set the port if you installed on Linux or OS X and add the "/owncloud" sub-URI:

    This will create a folder in your system. Every file you copied into this folder will be automatically sync to the ownCloud application.

    How to configure the email settings of ownCloud?

    This is required so your application can send notifications via email. If you are using the Native installers, you can configure it during the installation. If you are using the Virtual Machines or AMI's you can configure the email settings manually. You can find below an example of configuring the email using a GMail account.

    Edit the installdir/apps/owncloud/htdocs/config/config.php and add the following at the end of the file:

    ...
    "mail_smtpmode" => 'smtp',
    "mail_smtphost" => 'ssl://smtp.gmail.com:465',
    "mail_smtpauth" => true,
    "mail_smtpname" => 'your_account@gmail.com',
    "mail_smtppassword" => 'your_account_password',
    );
    ?>
    

    Note that you have to configured the admin email from the ownCloud admin panel: Settings -> Personal -> Email

    How to enable SSL?

    You can see how to configure Apache to enable SSL connections at How to enable SSL to access through https?

    How to debug ownCloud errors?

    Once Apache starts, it will create two log files, the access_log and the error_log /installdir/apache2/logs directory or in /var/log/httpd if you are using Amazon Linux or Red Hat Enterprise cloud images.

    In Virtual Machines, Cloud Images and Ubuntu based Bitnami Cloud Hosting images installdir is /opt/bitnami.

    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
    /installdir/ctlscript.sh : httpd started
    

    The main MySQL log file is created at /installdir/mysql/data/mysqld.log file.

    How to increase the allowed size of the uploaded files?

    ownCloud configures the max upload size in the installdir/apps/owncloud/conf/htaccess.conf file. By default is configured to 512M.

    ...
    <IfModule mod_php5.c>
    php_value upload_max_filesize 513M
    php_value post_max_size 513M
    php_value memory_limit 512M
    ...

    You can change these options to increase the size. Please, specify the size using "M" (i.e. 1000M) and not "G" (i.e. 1G). There is known issues with 2048M but 2000M is working fine.

    Remind to restart the Apache server after this change and also replace INSTALLDIR with your installation directory.

    How to modify the ownCloud trusted domains?

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

    /opt/bitnami/apps/owncloud/bnconfig --machine_hostname NEW_HOSTNAME
    

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

    'trusted_domains' =>
    array (
        0 => "FIRST_DOMAIN",
        1 => "SECOND_DOMAIN",
        2 => "THIRD_DOMAIN",
    ),
    
     
    Tag page (Edit tags)
    • No tags
    Page statistics
    132648 view(s), 20 edit(s) and 12608 character(s)

    Comments

    You must login to post a comment.

    Attach file

    Attachments

    FileSizeDateAttached by 
     owncloud-client.png
    ownCloud client configuration
    15.26 kB13:50, 7 Aug 2012AdminActions