Bitnami ownCloud for Huawei

Enterprise Cloud

Description

ownCloud is a flexible, open source file sync and share solution. Whether

using a mobile device, a workstation, or a web client, it provides the ability to

access files on any device in one simple-to-use, secure and controlled

solution.

First steps with the Bitnami ownCloud Stack

Welcome to your new Bitnami application running on Huawei Enterprise

Cloud! Here are a few questions (and answers!) you might need when first

starting with your application.

What is the administrator username set for me to log in to the

application for the first time?

Username: user

What is the administrator password?

To obtain the administrator password, click the "Remote Login" menu option

next to the server name in the Huawei Cloud Server Console. This will launch

a new browser window with an encrypted login session. The application

password will be displayed on the login welcome screen.

What SSH username should I use for secure shell access to

my application?

SSH username: root

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.

Find out how to obtain application credentials.

How to debug errors in your database?

The main log file is created at /opt/bitnami/mysql/data/mysqld.log on the

MySQL database server host.

How to start or stop the services?

Each Bitnami stack includes a control script that lets you easily stop, start and

restart services. The script is located at /opt/bitnami/ctlscript.sh. Call it without

any service name arguments to start all services:

sudo /opt/bitnami/ctlscript.sh start

Or use it to restart a single service, such as Apache only, by passing the

service name as argument:

sudo /opt/bitnami/ctlscript.sh restart apache

Use this script to stop all services:

sudo /opt/bitnami/ctlscript.sh stop

Restart the services by running the script without any arguments:

sudo /opt/bitnami/ctlscript.sh restart

Obtain a list of available services and operations by running the script without

any arguments:

sudo /opt/bitnami/ctlscript.sh

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 /opt/bitnami/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

/opt/bitnami/apps/owncloud/bnconfig file.

sudo mv /opt/bitnami/apps/owncloud/bnconfig /opt/bitnami/apps/owncloud/b

nconfig.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 create a full backup of ownCloud?

Backup

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.

Follow these steps:

Change to the directory in which you wish to save your backup:

cd /your/directory

Stop all servers:

sudo /opt/bitnami/ctlscript.sh stop

Create a compressed file with the stack contents:

sudo tar -pczvf application-backup.tar.gz /opt/bitnami

Restart all servers:

sudo /opt/bitnami/ctlscript.sh start

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

safe location.

Restore

Follow these steps:

Change to the directory containing your backup:

cd /your/directory

Stop all servers:

sudo /opt/bitnami/ctlscript.sh stop

Move the current stack to a different location:

sudo mv /opt/bitnami /tmp/bitnami-backup

Uncompress the backup file to the original directoryv

sudo tar -pxzvf application-backup.tar.gz -C /

Start all servers:

sudo /opt/bitnami/ctlscript.sh start

If you want to create only a database backup, refer to these instructions for

MySQL and PostgreSQL.

How to configure outbound email settings?

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

Edit the /opt/bitnami/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.

Troubleshooting Gmail SMTP issues

If you are using Gmail as the outbound email server and you are not able to

send email correctly, Google may be blocking sign-in attempts from your apps

or devices. Depending on whether or not you use Google Apps, the steps to

correct this will differ.

For Google Apps users

If you are a Google Apps user, you will need your administrator to allow users

to change the policy for less secure apps. If you are a Google Apps

administrator, follow these steps:

Browse to the Google Apps administration panel.

Click on "Security" and then "Basic settings".

Look for the section "Less secure apps" and then click on "Go to

settings for less secure apps".

Select "Allow users to manage their access to less secure apps".

For other Google users

If you do not use Google Apps, follow the steps in the following sections,

depending on whether 2-step verification has been enabled on the account or

not.

If 2-step verification has not been enabled on the account, follow these steps:

Browse to the "Less secure apps" page and log in using the account

you are having problems with. This option is typically required by many

popular email clients, such as Outlook and Thunderbird, and should not

be considered unsafe.

Select the "Turn on" option.

If 2-step verification has been enabled on the account, you have to generate

an app password. Follow these steps:

Browse to the "App passwords" page.

Click "Select app" and choose the app you're using.

Click "Select device" and choose the device you're using.

Click the "Generate" button.

Enter the app password on your device.

Click the "Done" button.

Here are other options you may try:

Browse to the web version of Gmail and sign in to your account.

Once you're signed in, try to enable access for the application again.

Browse to the "Unlock Captcha" function page and sign in with your

Gmail username and password.

Disable IMAP from the Gmail web server interface and enable it again.

How to upload files to the server with SFTP?

Although you can use any SFTP/SCP client to transfer files to your server, the

link below explains how to configure FileZilla (Windows, Linux and Mac OS

X), WinSCP (Windows) and Cyberduck (Mac OS X). It is required to use your

server's private SSH key to configure the SFTP client properly. Choose your

preferred application and follow the steps in the link below to connect to the

server through SFTP.

How to upload files to the server

How to enable HTTPS support with SSL

certificates?

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 /opt/bitnami/apache2/conf/bitnami/bitnami.conf

Certificate file /opt/bitnami/apache2/conf/server.crt

Certificate key file /opt/bitnami/apache2/conf/server.key

Variable Value

CA certificate

bundle file (if

present)

/opt/bitnami/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 /opt/bitnami/apache2/conf/bitnami/bitnami.conf

Directive to include

(Apache v2.4.8+)

SSLCACertificateFile

"/opt/bitnami/apache2/conf/server-ca.crt"

Directive to include

(Apache < v2.4.8)

SSLCertificateChainFile

"/opt/bitnami/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 /opt/bitnami/apache2/conf/server*

sudo chmod 600 /opt/bitnami/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 create an SSL certificate?

You can create your own SSL certificate with the OpenSSL binary. 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).

Create your private key (if you haven't created it already):

sudo openssl genrsa -out /opt/bitnami/apache2/conf/server.key 2048

Create a certificate:

sudo openssl req -new -key /opt/bitnami/apache2/conf/server.key -o

ut /opt/bitnami/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 /opt/bitnami/apache2/conf/cert.csr -out /opt

/bitnami/apache2/conf/server.crt -req -signkey /opt/bitnami/apach

e2/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 /opt/bitnami/apache2/conf/server.key -o

ut 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 /opt/bitnami/apache2/conf/se

rver.key

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

How to force HTTPS redirection?

Add the following to the top of the /opt/bitnami/apps/owncloud/conf/httpd-

prefix.conf file:

RewriteEngine On

RewriteCond %{HTTPS} !=on

RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [R,L]

After modifying the Apache configuration files, restart Apache to apply the

changes.

How to debug Apache errors?

Once Apache starts, it will create two log files at

/opt/bitnami/apache2/logs/access_log and /opt/bitnami/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

How to modify PHP settings?

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

/opt/bitnami/php/etc/php.ini.

After modifying the PHP configuration file, restart both Apache and PHP-FPM

for the changes to take effect:

sudo /opt/bitnami/ctlscript.sh restart apache

sudo /opt/bitnami/ctlscript.sh restart php-fpm

For example, to modify the default upload limit for PHP, update the PHP

configuration file following these instructions.

How to modify the allowed limit for uploaded

files?

Modify the following options in the /opt/bitnami/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 /opt/bitnami/ctlscript.sh restart apache

sudo /opt/bitnami/ctlscript.sh restart php-fpm

How to access phpMyAdmin?

For security reasons, phpMyAdmin is accessible only when using 127.0.0.1

as the hostname. To access it from a remote system, you must create an

SSH tunnel that routes requests to the Apache Web server from 127.0.0.1.

This implies that you must be able to connect to your server over SSH in

order to access these applications remotely.

IMPORTANT: Before following the steps below, ensure that your Apache and

MySQL servers are running.

NOTE: The steps below suggest using port 8888 for the SSH tunnel. If this

port is already in use by another application on your local machine, replace it

with any other port number greater than 1024 and modify the steps below

accordingly. Similarly, if you have enabled Varnish, your stack's Apache Web

server might be running on port 81. In this case, modify the steps below to

use port 81 instead of port 80 for the tunnel endpoint.

Windows

To access the application using your Web browser, create an SSH tunnel, as

described below.

Download PuTTY and make sure you can log in to the server console

with it following the instructions in the FAQ. Once you have confirmed

you are able to log in successfully, log back out.

Reconnect to the server using PuTTY, this time adapting the steps to

include an additional SSH tunnel. When configuring the new SSH

session in PuTTY, additionally navigate to the "Connection -> SSH ->

Tunnels" section and create a secure tunnel by forwarding port 80 on

the server to port 8888 on the local host (127.0.0.1 or localhost).

Click the "Add" button to add the secure tunnel configuration to the

session. Here is an example:

Go back to the "Session" section and save your changes by clicking

the "Save" button.

Click the "Open" button to open an SSH session to the server. The

SSH session will now include a secure SSH tunnel between the two

specified ports.

While the tunnel is active, you should be able to access the phpMyAdmin

console through the secure SSH tunnel you created, by browsing to

http://127.0.0.1:8888/phpmyadmin.

To log in, use username root for MySQL and the application password from

the detail page for your cloud server.

If you are unable to access phpMyAdmin, verify that the SSH tunnel was

created by checking the PuTTY event log (accessible via the "Event Log"

menu):

Linux and Mac OS X

To access the application using your Web browser, create an SSH tunnel, as

described below.

Open a new terminal window on your local system (for example, using

"Finder -> Applications -> Utilities -> Terminal" in Mac OS X or the

Dash in Ubuntu).

Make sure you can log in to the server console following the

instructions in the FAQ. Once you have confirmed you are able to log in

successfully, log back out.

Run the following command to configure the SSH tunnel. Remember to

replace SERVER-IP with the public IP address or hostname of your

server. Enter your SSH password when prompted.

ssh -N -L 8888:127.0.0.1:80 bitnami@SERVER-IP

If you are using a private key to connect to the server, use the following

command instead, remembering to replace KEYFILE with the path to

your private key and SERVER-IP with the public IP address or

hostname of your server:

ssh -N -L 8888:127.0.0.1:80 -i KEYFILE bitnami@SERVER-IP

NOTE: If successful, the above commands will create an SSH tunnel

but will not display any output on the server console.

While the tunnel is active, you should be able to access the phpMyAdmin

console through the secure SSH tunnel you created, by browsing to

http://127.0.0.1:8888/phpmyadmin.

To log in, use username root for MySQL and the application password from

the detail page for your cloud server.

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.

Enter your username and password and click "Next".

Specify whether to sync everything or only selected files. Also, specify

a location for the local files to reside.

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 "/opt/bitnami/php/bin/php -f /opt/b

itnami/apps/owncloud/htdocs/cron.php > /dev/null 2>&1"

Note that the cron job will be executed by the daemon user.

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:

sudo apt-get update

sudo apt-get install 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".

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 = /opt/bitnami/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 /opt/bitnami/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 pr

int all 397 lines

Apply the configuration with this command

sudo /etc/init.d/fail2ban restart

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 improve 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 p

lease configure a memcache if available. Further information can b

e found in our documentation.

ownCloud recommends configuring caching. It improves performance

by storing data, code, and other objects in memory. Find out more.

You are accessing this site via HTTP. We strongly suggest you conf

igure your server to require using HTTPS instead as described in o

ur security tips.

ownCloud also suggests access using HTTPS instead of HTTP. Find

out more.

The "Strict-Transport-Security" HTTP header is not configured to

least "15768000" seconds. For enhanced security we recommend enabl

ing HSTS as described in our security tips.

To follow this suggestion, add the line below in the

/opt/bitnami/apps/owncloud/conf/httpd-app.conf file:

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

cludeSubDomains; preload"

How to increase the available disk space for

ownCloud?

If your ownCloud instance is running short of disk space for files, you can

increase the available disk space by changing the server type and selecting a

server with higher storage capacity. Refer to the FAQ for more information

on this.

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.

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.

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.

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

/opt/bitnami/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

/opt/bitnami/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.

Open a web browser and log into your ownCloud interface.

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

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".

Select an image file and click "Open".

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

Switch to the desktop client. Confirm that the file you uploaded to the

web interface appears in the "Activity" tab.

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

How to upgrade ownCloud?

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.

Upgrading from the ownCloud admin panel

ownCloud already has an "Updater" 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 /opt/bitnami/apps/owncloud/htdocs

sudo chmod 644 /opt/bitnami/apps/owncloud/htdocs/.user.ini

Run the upgrade process from the admin panel by navigating to

"Admin -> Update center" and running the upgrade process.

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

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

sudo chmod 444 /opt/bitnami/apps/owncloud/htdocs/.user.ini

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

/bitnami/apps/owncloud/htdocs/apps

You should now be able to access your new ownCloud application. Find more

information.

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

From the ownCloud 4.0.x installation, back up the directories

/opt/bitnami/apps/owncloud/data and

/opt/bitnami/apps/owncloud/htdocs/config.

Export the database using phpMyAdmin. After logging in, select the

bitnami_owncloud database and click the "Export" button. Export the

database using the default parameters.

Uninstall the ownCloud 4.0.x installation keeping the full backup done

before.

Install ownCloud 4.5.x.

After the installation is complete, copy the data folder saved from the

4.0.x installation to the new /opt/bitnami/apps/owncloud/data location.

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

/opt/bitnami/apps/owncloud/htdocs/config/config.php file.

Copy the config folder from the 4.0.x installation updated with the new

dbpassword parameter to the new

/opt/bitnami/apps/owncloud/htdocs/config location.

Access the new phpMyAdmin installation and log in. Select the

bitnami_owncloud database and remove all tables.

Click the "Import" button and import your saved file with the default

options.

Click 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 ;

Restart the Apache server and browse to your upgraded application.

Full stack upgrade from ownCloud 6.0.x to ownCloud 7.0.x

From the ownCloud 6.0.x installation, back up the directories

/opt/bitnami/apps/owncloud/data and

/opt/bitnami/apps/owncloud/htdocs/config.

Export the database using phpMyAdmin. After logging in, select the

bitnami_owncloud database and click the "Export" button. Export the

database using the default parameters.

Uninstall the ownCloud 6.0.x installation keeping the full backup done

before.

Install ownCloud 7.0.x.

After the installation is complete, copy the data folder saved from the

6.0.x installation to the new /opt/bitnami/apps/owncloud/data location.

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

/opt/bitnami/apps/owncloud/htdocs/config/config.php file. Modify the

version parameter to match the new one.

Copy the config folder from the 6.0.x installation updated with the new

dbpassword parameter to the new

/opt/bitnami/apps/owncloud/htdocs/config location.

Access the new phpMyAdmin installation and log in. Select the

bitnami_owncloud database and remove all tables.

Click the "Import" button and import your saved file with the default

options.

Click the "SQL" button and execute the following SQL commands to

add the permissions column in the filecache table:

ALTER TABLE oc_filecache ADD permissions int(11);

Restart the Apache server and browse to your upgraded application.

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.

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.

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).

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.

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.

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.