Update: I've updated the titles for the first two articles in my Nextcloud series to explicitly identify the target environment being a "sandbox". The purpose of the sandbox is to develop comfort with Nextcloud before deploying to a production instance where the safety and security of data become critical. I have another article which provides step-by-step instructions for a secure production deployment.
In my previous article I described my first steps towards separation from Microsoft Office 365. Specifically, I outlined how to set-up Vimwiki for use as a OneNote replacement.
Vimwiki is very good, but a complete replacement requires a private cloud combined with a file sync-n-share application which can allow me to control and protect my data. The sync-n-share application I want to use is Nextcloud. For a well written background on Nextcloud's origin check out this article.
My first major activity is to install and start using Nextcloud in a dev VM environment so I can gain some comfort with administering and using the application.
This will be a quite a manual install compared to what is possible using the snap package. However, I specifically want to take a deliberate approach for both my understanding and to facilitate customization.
At least some familiarity with installing Linux and working at the command line is assumed for following this tutorial.
I completed the following using the Ubuntu Server 16.04 with LTS (Xenial Xerus). Download the ISO located on the Ubuntu site or try with a later LTS version: https://www.ubuntu.com/download/server
You should be able to achieve the same using Virtual Box on Windows, Mac and most Linux distros following roughly similar steps.
Open the KVM Virtual Machine Manager GUI:
In the GUI Click the Create a new virtual machine button.
Creating the VM is a fairly straight-forward five step process:
- Leave the default as Local install media (ISO image or CDROM) and continue.
- Select the Use ISO image: option and type or paste the path to the downloaded ISO image and continue.
- Leave the defaults to "1024" MiB and "1" CPUs. The RAM will become quite important later as you make decisions for production deployment as it will drive cloud provider costs but for now this should be fine.
- Use default Create a disk image for the virtual machine. For initial development purposes I will only use 20.0 GiB.
- Give it a meaningful name, I'll use "cloud1", and click finish.
KVM should open a console immediately to begin the install.
In production, choices for both storage and RAM will become quite important. But at this point we can make more arbitrary choices as get used to the application.
Installing the OS
Instead of going through every Ubuntu install screen here I will point you in the direction of this tutorial on howtoforge.
The only major difference is that we will be using "cloud1.example.vm" for the hostname.
Also, you can skip 8. Configure the Network as I'll be covering that part explicitly in the next section.
Note that we could install the entire LAMP (Linux, Apache, MySQL, PHP) stack during the Ubuntu install Software selection step. This would be a simpler experience but I'll be doing each install & configuration deliberately for understanding & customization (particularly with regards to use of MariaDB).
Once the install is complete, but before continuing with the network setup, we should upgrade the packages installed from the distribution's ISO. Note that this this may take some time.
sudo apt update sudo apt upgrade
KVM will give us a dynamic IP but we need a static one for our server.
The KVM NAT network is 192.168.122.0 and the guest's interface name is ens3. If these are different for you please make the appropriate substitutions.
Edit the network interfaces file:
Update the interface description which follows the commented line "# The primary network interface":
auto ens3 iface ens3 inet static address 192.168.122.20 netmask 255.255.255.0 network 192.168.122.0 broadcast 192.168.122.255 gateway 192.168.122.1 dns-nameservers 220.127.116.11 18.104.22.168
Restart the networking service:
sudo service networking restart
Next we want to add hostnames but first let's test that the networking is still working.
From the guest:
From the host:
In production we will rely on DNS, but for initial development we will add an entry in the hosts file of the KVM host for static hostname look-up:
Add this line:
192.168.122.20 cloud1.example.vm cloud1
Test that this works from the KVM host with:
You should get a response similar to:
PING cloud1.example.vm (192.168.122.20) 56(84) bytes of data. 64 bytes from cloud1.example.vm (192.168.122.20): icmp_seq=1 ttl=64 time=0.292 ms 64 bytes from cloud1.example.vm (192.168.122.20): icmp_seq=2 ttl=64 time=0.367 ms
At this point you can set up ssh access from the host or continue working in the KVM console. I'm not going to cover it here for the purpose of brevity but I would recommend ssh for better productivity.
MySQL and MariaDB should work equally well for Nextcloud. While MySQL remains the standard for the LAMP stack on Ubuntu (CentOS prefers MariaDB), I decided to use MariaDB because it is a community-driven project with a team that delivers quicker security updates `this article <described here.
First, install the server & client packages:
sudo apt install mariadb-server mariadb-client
The service should be running, you can check using:
systemctl status mysql
On many LAMP installation tutorials you may be recommended to run the mysql_secure_installation script.
This is not necessary for MariaDB on Ubuntu 16.04 as:
- MariaDB is now installed on Ubuntu with the root user authenticated using the unix_socket plugin.
- The anonymous user is no longer created on installation
- The root users is only included for Host='localhost' on installation
- The test database is no longer included on installation
Set-up MariaDB for Nextcloud
First we need to configure MariaDB so it will work for Nextcloud. We will create a specific config file with (hopefully) self-explanatory comments as to what is being done. To find out why, see: https://docs.nextcloud.com/server/11/admin_manual/configuration_database/linux_database_configuration.html
Add the following:
# Nextcloud database configuration file [mysqld] # disable binary logging skip-log-bin # use transaction read committed isolation transaction-isolation=read-committed # enable emojis innodb_large_prefix=true innodb_file_format=barracuda innodb_file_per_table=true
Restart the service:
sudo systemctl restart mysql
Login as root:
sudo mysql -uroot
Verify variables reflect the configuration file created above:
SHOW GLOBAL VARIABLES LIKE 'log_bin'; SHOW GLOBAL VARIABLES LIKE 'tx_isolation'; SHOW GLOBAL VARIABLES LIKE 'innodb_large_prefix'; SHOW GLOBAL VARIABLES LIKE 'innodb_file_format'; SHOW GLOBAL VARIABLES LIKE 'innodb_file_per_table';
Create the database and user. We will call the user oc_nextadmin in alignment with the use of the oc_ prefix for all tables (note: oc stands for ownCloud the project Nextcloud was forked from).
Replace apassword with the password you will be using. This is required with a subsequent install step, however, for regular use you will only need to use use the application administrator password.
CREATE DATABASE nextcloud CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci; CREATE USER oc_nextadmin@localhost IDENTIFIED BY 'apassword'; GRANT ALL PRIVILEGES ON nextcloud . * TO oc_nextadmin@localhost; FLUSH PRIVILEGES;
You can now exit as the Nextcloud install script will handle all other database tasks.
Install & Set-up Apache
There's not much to say about the Apache install so I'll cover both install & set-up together.
sudo apt install apache2
To confirm the service is running:
systemctl status apache2
Create the Nextcloud site config file
Add these lines as recommended in the Nextcloud installation manual:
Alias /nextcloud "/var/www/nextcloud/" <Directory /var/www/nextcloud/> Options +FollowSymlinks AllowOverride All <IfModule mod_dav.c> Dav off </IfModule> SetEnv HOME /var/www/nextcloud SetEnv HTTP_HOME /var/www/nextcloud </Directory>
Enable the site:
sudo ln -s /etc/apache2/sites-available/nextcloud.conf /etc/apache2/sites-enabled/nextcloud.conf
The Apache module rewrite is required. Nextcloud also recommendations headers, env, dir, mime and ssl. Let's make sure all of these modules as well as the default SSL site are enabled:
sudo a2enmod rewrite headers env dir mime ssl sudo a2ensite default-ssl sudo service apache2 restart
Install PHP 7.0
There are a number of PHP modules which Nextcloud depends on. We will install them in a single command including the modules for integration with Apache & MariaDB.
sudo apt install php7.0-common php7.0-cli php7.0-bz2 php7.0-curl php7.0-gd php7.0-intl php7.0-mbstring php7.0-mcrypt php7.0-mysql php7.0-mysql php7.0-xml php7.0-zip libapache2-mod-php7.0
You can see that all the required/recommended modules are installed & enabled:
php -m | grep -E "bz2|ctype|curl|dom|fileinfo|gd|iconv|intl|json|libxml|mbstring|mcrypt|openssl|pdo_mysql|posix|SimpleXML|xmlwriter|zip|zlib"
Confirm PHP-Apache integration:
echo "<?php phpinfo(); ?>" | sudo tee /var/www/html/test.php
Navigate to http://cloud1.example.vm/test.php in your KVM host's web browser. You should see something like:
You don't need the file anymore so remove it.
sudo rm /var/www/html/test.php
Download & Install Nextcloud 11
I'm downloading Nextcloud 11.0.0. You should go to the Nextcloud download site and download the latest stable version. I downloaded the .tar.bz2 archive although there is also a .zip archive.
Verify the integrity of the file then expand the archive to the Apache server directory.
Replace 11.0.0 with whatever version you downloaded. Note the v - verbose - flag is optional.
sudo tar -xvjf nextcloud-11.0.0.tar.bz2 -C /var/www/
Temporarily change the owner of the Nextcloud directory to the HTTP user.
sudo chown -R www-data:www-data /var/www/nextcloud/
Run the command line installation as the HTTP user from that directory. Of course, change the capitalized passwords to your own. Note again that you will need to use the admin-pass regularly but not the database-pass.
cd /var/www/nextcloud/ sudo -u www-data php occ maintenance:install \ --database "mysql" --database-name "nextcloud" \ --database-user "oc_nextadmin" --database-pass "DBPASS" \ --admin-user "nextadmin" --admin-pass "ADMINPASS"
If you see this, the install is successful!
Nextcloud is not installed - only a limited number of commands are available Nextcloud was successfully installed
Final Server Configuration Pieces
Harden the security of the server by running the script that is recommended in the Nextcloud manual.
Copy the entire script text (which starts #!/bin/bash) to a file say nextcloud_harden.sh.
Make it executable:
chmod +x nextcloud_harden.sh
The last installation step is to add the host name and static IP by editing the php config file:
Update the trusted_domains variable to:
'trusted_domains' => array ( 0 => 'localhost', 1 => '192.168.122.20', 2 => 'cloud1.example.vm', ),
Finally, tell Apache to reload configurations:
sudo service apache2 reload
Install Confirmation & Login
From your KVM host's web browser navigate to https://cloud1.example.vm/nextcloud
Since your SSL certificate is not signed by a certificate authority your browser should tell you something like:
In Firefox, for example, click "Advanced" > "Add Exception..." > "Confirm Security Exception".
When in production, you may want to consider Let's Encrypt
You should see a login screen where you can enter your app admin info and click "Log in".
If you see this final picture you've succeeded!
Now you can go ahead and try it out - add some users and play around with file management. You'll want to start syncing with a client to really test it out.
In future articles I plan to write on Nextcloud production options.