Skip to main content

How to Setup a Raspberry Pi Nextcloud Server

As time goes on the protection of your own privacy with 3rd party companies becomes harder and harder. This is where software like Nextcloud comes in hand, as it gives you full control over your files with no 3rd party controller.

It is important to remember that since your data will be stored on your local network you will end up using a lot of bandwidth when uploading and downloading files from outside your local network. If your internet connection is not great then you may not get the best experience if you plan on using it outside your local network.

If this looks familiar then that’s because it likely is, Nextcloud is an actively maintained fork of the owncloud software that I have previously covered. The longer it’s in development the more different these two software packages will likely become, I suggest looking into both and then deciding on which one to go with.

If you want to learn more about Nextcloud, you can check out the nextcloud website.

Note: The USB ports on a Raspberry Pi are typically unable to power an external hard drive. If you find this the case and your hard drive doesn’t use an external power supply then I recommend looking into buying a powered USB hub for the Pi.

Equipment List

You can find all the bits and pieces that I used/recommend for this Raspberry Pi nextcloud tutorial right below.

Recommended

Raspberry Pi 2 or 3

Micro SD Card or a SD card if you’re using an old version of the Pi.

Power Supply

Ethernet Cord or Wifi dongle (Pi 3 has WiFi inbuilt)

External Hard drive or USB Drive

Optional

Raspberry Pi Case

USB Keyboard

USB Mouse

Installing Apache and PHP

To run Nextcloud on the Raspberry Pi we will first need to install and setup Apache and PHP.

We won’t be going too in-depth into installing these as they are a minor components to this tutorial.

If you want to learn more about setting up a Web Server, then be sure to follow our tutorial on how to do this.

For the best performance I recommend using Raspbian lite but just normal Raspbian will also work just as well.

If you need information on how to set this all up check out the guide in the Pi operating systems section.

For this tutorial, we will make use of the latest available version of PHP 7.

1. To get started let’s first update our package repositories with the following command:

sudo apt update
sudo apt upgrade

2. With that done, let’s now install apache with the following command:

sudo apt install apache2

You can check to make sure Apache2 is successfully up and running by going to your Pi’s IP address, this should load a default Apache Page.

If you are unsure on what your Raspberry Pi’s local IP address is then type in hostname -I into the terminal.

3. With Apache2 now installed onto the Raspberry Pi we just need to install PHP and several of its packages.

For this tutorial we will be using PHP 7.3, this will require that you have Raspbian Buster installed.

You can upgrade to Raspbian buster by following our guide.

To install PHP and the packages we need, run the following command.

sudo apt install php7.3 php7.3-gd php7.3-sqlite3 php7.3-curl php7.3-zip php7.3-xml php7.3-mbstring php7.3-mysql php7.3-bz2 php7.3-intl php7.3-smbclient php7.3-imap php7.3-gmp

4. With Apache and PHP now installed there is one final thing we need to do, and that is to restart Apache.

You can do this ny making use of the following command:

sudo service apache2 restart 

Setting up a MySQL Database and User for Nextcloud

In this section we will be showing you how to set up a user and database for Nextcloud to use to store its data.

Before beginning this section you must have set up a MySQL server on your Raspberry Pi already.

1. The first thing we need to do is open the MySQL command line tool by running the following command.

We will be using this command line tool to create a user and database for MySQL.

sudo mysql -u root -p

2. Once you have logged in to the tool, we can start by creating a database.

We will be creating this database called nextclouddb by running the following command.

CREATE DATABASE nextclouddb;

3. Our next step is to create a user that we will be using to interact with our new database.

We will be creating a user called nextclouduser by running the command below. Make sure that you replace [PASSWORD] with a secure password and make note of it for later.

CREATE USER 'nextclouduser'@'localhost' IDENTIFIED BY '[PASSWORD]';

4. With our user created we need to now give it permissions to interact with our database.

We can do that by running the following command.

GRANT ALL PRIVILEGES ON nextclouddb.* TO 'nextclouduser'@'localhost';

This command grants the user nextclouduser all privileges on the nextclouddb database and all of its tables.

5. Our final task is to flush the privilege table.

To flush the privileges all we need to do is run the following command.

FLUSH PRIVILEGES;

With this done, we can now proceed to install Nextcloud on our Raspberry Pi.

Downloading Nextcloud on your Raspberry Pi

Getting Nextcloud on your the Raspberry Pi is quite simple, it mainly involves downloading the zip file from their website, extracting it and then making some .

1. To get started let’s first move to our html directory with the following command:

cd /var/www/

2. Now we can download the latest version of Nextcloud to our device.

To do this we will use wget to download the latest release to the current folder.

sudo wget https://download.nextcloud.com/server/releases/latest.tar.bz2

3. With Nextcloud now downloaded to our Raspberry Pi, let us extract the archive.

To extract the archive using tar we need to use the command below.

sudo tar -xvf latest.tar.bz2

4. We now need to create a data directory for Nextcloud to operate in, for the initial setup of Nextcloud we must make this folder in our html/nextcloud directory.

Create the directory by using the following command:

sudo mkdir -p /var/www/nextcloud/data

5. Now let’s give the correct user and group control over the entire Nextcloud folder and everything inside it by running the following command.

sudo chown -R www-data:www-data /var/www/nextcloud/

6. Finally we need to give it the right permissions, again run the following command:

sudo chmod 750 /var/www/nextcloud/data

Configuring Apache for Nextcloud

Next, we need to deal with the .htaccess file for Nextcloud.

Since we installed Nextcloud into the default Apache2 directory /var/www/, we will need to change some settings in Apache2 to allow the .htaccess file to override settings.

To handle this just for the Nextcloud directory we will be creating a new configuration file.

1. To get started let’s create a file which will store our configuration changes for Nextcloud:

sudo nano /etc/apache2/sites-available/nextcloud.conf

2. Within this file enter the following lines.

Alias /nextcloud "/var/www/nextcloud/"

<Directory /var/www/nextcloud/>
  Require all granted
  AllowOverride All
  Options FollowSymLinks MultiViews

  <IfModule mod_dav.c>
    Dav off
  </IfModule>

</Directory>

These lines basically tell Apache2 how to handle itself within the /var/www/nextcloud/ folder.

These changes will allow Apache2 to read and utilize the .htaccess files within the Nextcloud directory.

3. Now we can save and quit out of the file by pressing CTRL + X then pressing Y and then ENTER.

4. With the file created we now need to tell Apache to make use of it.

We can do this by utilizing the a2ensite command followed by nextcloud.conf.

sudo a2ensite nextcloud.conf

5. Now we need to restart Apache2 to force it to read in the updated configuration file. We can do that easily with the following command:

sudo systemctl reload apache2

With that done you can now move on to setting up the Nextcloud software within its web interface.

Nextcloud Initial Setup

1. Now that we have finished with that we can now finally go to Nextcloud itself and begin its installation process.

To begin go to your Raspberry Pi’s IP address plus /nextcloud.

If you don’t know your Raspberry Pi’s IP address you can make use of the command hostname -I.

Remember to replace [IPADDRESS] with that of your Raspberry Pi’s.

[IPADDRESS]/nextcloud

2. You will now be greeted with the following screen.

Here you will need to type in the Username and Password (1.) that you intend to use for your admin account.

If you plan on allowing your Nextcloud file service to be accessible from outside your network, make sure that you use a long and secure password.

Next, we need to specify the details for our database server. To get to these options you will need to click the “Storage & Datbase” option (2.).

Now you need to slect the type of database we want to use. As we are using an SQL server click the “MySQL/MariaDB” (3.) option.

Finally we need to enter the details for our database server. There are three bits of information that we will need to enter.

  1. The username for the user that will interact with our database server. (A.) If you are using the same information we used, this setting should be set to nextclouduser.
  2. The password that you set for the above user. (B.)
  3. The final option you will need to set is the database name. (C.) If you have been following our guide this will be nextclouddb.

Once you are happy with this, press the “Finish Setup” button (4.), please note this can take some time to complete as it finalises your setup.

Raspberry Pi Nextcloud Set up Screen

3. After this you should now be greeted with the following welcome screen, this just lays out the various programs you can use to connect with your Nextcloud installation.

Just click the X button in the top right corner to continue.

Nextcloud Welcome Screen

4. Now you can finally see the interface of the Raspberry Pi Nextcloud, you should take some time to familiarize yourself with all the functionality of Nextcloud’s interface.

We won’t go too in depth on how to use the Nextcloud interface, if you need more information then I recommend checking out the support section on nextcloud.

We have however highlighted some of the key areas to check out in the screenshot below.

Nextcloud Files Screen

Moving Nextcloud’s data folder

With Nextcloud now safely installed we can now tweak the setup to both be more secure and a bit more useable. One of the first things we should do is move the data directory so it does not sit in our web accessible directory.

This is also the same way you would move your Nextcloud data directory onto a larger external hard drive rather than putting increased load onto the Raspberry Pi’s SD Card.

1. To get started let’s make our new directory for where we will store our data files.

To make it easy we will make a new folder at /var/nextcloud and move our data folder into there.

Create the folder by running the following command:

sudo mkdir -p /var/nextcloud

2. With our new folder we created we will now move our data directory into it, this is easy to do thanks to the mv command.

Please note that your Nextcloud system will be out of action while we move the file then adjust the configuration file.

To begin the move type in the following command:

sudo mv -v /var/www/nextcloud/data /var/nextcloud/data

3. Now with the files moved over we can now modify the datadirectory configuration to point to our new directory.

First, let’s change to the config directory for Nextcloud with the following command.

cd /var/www/nextcloud/config

4. We can now copy the config file to make a backup of the file, we can do this with the following command:

sudo cp -p config.php config.php.bk

5. Finally let’s open up the config.php file for editing using nano.

sudo nano config.php

6. Within this file we need to change the following line:

'datadirectory' => '/var/www/nextcloud/data',

To

'datadirectory' => '/var/nextcloud/data',

7. Now we can save and quit out of the file by pressing CTRL + X then Y and then ENTER.

8. As one last precuation we should make sure that the www-data user still has ownerships over our new folder.

sudo chown -R www-data:www-data /var/nextcloud/data

You should be able to now refresh your web browser and all your files should be showing exactly as they were previously.

Increasing Nextcloud’s max upload size

By default, PHP has a very low upload limit, so low it’s only 2 MB. To change this, we need to modify the php.ini file and increase the limit. A cloud storage system wouldn’t be very useful if you could only ever upload 2mb files.

1. To get started we need to begin editing the configuration file with the following command:

sudo nano /etc/php/7.3/apache2/php.ini

2. Now we need to find and replace the following two lines.

post_max_size = 8M
upload_max_filesize = 2M

To

post_max_size = 1024M
upload_max_filesize = 1024M

Of course, you can set the file size limits to something that is much higher than 20M, so feel free to change that number to whatever you think is the maximum size file you will upload to your Nextcloud.

3. Now we can save and quit out of the file by pressing CTRL + X then pressing Y and then ENTER.

Now we need to restart Apache2 to force it to read in the updated configuration file. We can do that easily with the following command:

sudo service apache2 restart

4. You should now be able to restart your web browser and begin a new upload to see that the maximum upload size has been increased successfully.

Setting up SSL for Nextcloud

Now we should really work on setting up your Raspberry Pi Nextcloud server so that it runs through HTTPS and not plain HTTP.

For this tutorial, we will assume that you do not have a domain name, so we will be generating our own self signed certificate and not utilizing one from a free service such as Letsencrypt.

1. Before we go modifying our Apache2 configuration we will first generate the self-signed certificate, luckily, we can do this all in one command thanks to OpenSSL.

Remember that a self-signed certificate will throw errors in your web browser and is not as secure as a properly signed certificate but it is better than nothing. It is also the only option if you’re not utilizing a domain name.

Before we generate the certificate, let’s first make a directory to store it.

sudo mkdir -p /etc/apache2/ssl

2. Now let’s generate the certificate itself by running the following command in the terminal:

sudo openssl req -x509 -nodes -days 365 -newkey rsa:4096 -keyout /etc/apache2/ssl/apache.key -out /etc/apache2/ssl/apache.crt

If you want to know exactly what these command arguments do, then read our little description below.

req: This specifies a subcommand for X.509 certificate signing request (CSR) management.

-x509: This option specifies that we want to make a self-signed certificate file instead of generating a certificate request.

-nodes: This tells the openssl application that we don’t want to specify a passphrase, a passphrase will require us to enter it every time Apache is restarted which is painful to deal with.

-days 365: This specifies the amount of days we want the certificate to remain valid for, after this amount of days you will have to generate a new certificate.

-newkey rsa:4096: This will create the certificate request and a new private key at the same time. You will need to do this since we didn’t create a private key in advance. The rsa:2048 tells OpenSSL to generate an RSA key that is 2048 bits long.

-keyout: This parameter names the output file for the private key file that is being created.

-out: This option names the output file for the certificate that we are generating.

After pressing enter you will be presented with the following options to fill out.

Country Name (2 letter code) [AU]:
State or Province Name (full name) [Some-State]:
Locality Name (eg, city) []:
Organization Name (eg, company) [Internet Widgits Pty Ltd]:
Organizational Unit Name (eg, section) []:
Common Name (e.g. server FQDN or YOUR name) []:
Email Address []:

3. Once you have filled out all that information we can then proceed on with setting up Apache2 to run SSL and to also utilize our newly generated certificate. This is a simple process but an important one.

First let’s enable the SSL module for Apache with the following command:

sudo a2enmod ssl

4. Now we need to modify the default-ssl.conf file so it will utilize our new certificates and not the default ones that are generated by OpenSSL on installation.

To begin modifying this file run the following command:

sudo nano /etc/apache2/sites-available/default-ssl.conf

5. Within this file we need to change the two lines below to point to our new certificates we generated into our /etc/apache2/ssl folder.

Change

SSLCertificateFile /etc/ssl/certs/ssl-cert-snakeoil.pem
SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key

To

SSLCertificateFile /etc/apache2/ssl/apache.crt
SSLCertificateKeyFile /etc/apache2/ssl/apache.key

6. Now we can save and quit out of the file by pressing CTRL + X then pressing Y and then Enter.

7. We can now enable the default-ssl configuration and restart Apache to load in our new configuration. We can do this with the following two commands.

sudo a2ensite default-ssl.conf
sudo service apache2 restart

8. You can test to make sure this is working by going to your Raspberry Pi’s IP address with https:// in front of it. It will give you a warning about it potentially being an invalid certificate. This is normal as it is an unsigned certificate.

For instance to make sure my own copy of Nextcloud is now running behind SSL I would go to the following.

https://192.168.1.105/nextcloud

Steps 9, 10, 11 and 12 are all optional and don’t need to be completed.

9. An optional extra step to ensure that you have the best security for your Nextcloud setup is to enforce SSL so no connection can be made over HTTP, if a connection is made it will redirect you to HTTPS.

We can do this by making some changes to our apache configuration, to begin let’s edit the default file with the following command:

sudo nano /etc/apache2/sites-available/000-default.conf

10. Replace all the text in this file with the code below. This will basically redirect all HTTP traffic to its HTTPs equivalent.

<VirtualHost *:80>
   ServerAdmin example@example

   RewriteEngine On
   RewriteCond %{HTTPS} off
   RewriteRule ^(.*)$ https://%{HTTP_HOST}$1 [R=301,L]
</VirtualHost>

11. Now we can save and quit out of the file by pressing CTRL + X then pressing Y and then ENTER.

12. Now before this will work we need to enable the redirect module and restart apache. We can easily achieve this by running the following two commands:

sudo a2enmod rewrite
sudo service apache2 restart

Now going to your Raspberry Pi on HTTP should automatically redirect to the HTTPS version. For example, if I go to http://192.168.1.105 it will redirect to https://192.168.1.105

Port Forwarding Nextcloud

Finally, onto the section about port forwarding Nextcloud. We won’t go into too much depth on the ins and outs of port forwarding for your router but we will tell you what ports need forwarding. We will also mention what changes need to be made to Nextcloud for this to work.

Before we get started with this section you need to know that Nextcloud will only operate under specifically specified trusted domains. Which means you will need to either specify a domain name that you want to use for your connection or use your public IP address.

Since most home public IP addresses are dynamic you will need to look into setting up a dynamic DNS service, you will find our tutorial on how to setup a dynamic DNS service for your Raspberry Pi very handy.

1. To add your domain/IP we need to modify NextCloud’s configuration file, we can do that by running the following command:

sudo nano /var/www/nextcloud/config/config.php

2. Within this file you will see a block of text like below. This is an array of all trusted domains that you allow Nextcloud to operate through. For now, it should only include your Raspberry Pi’s local IP address. We will add our new domain/IP onto the end of this array.

'trusted_domains' =>
array (
    0 => '192.168.1.105',
),

For our example, we will be adding nextcloud.pimylifeup.com to the array. This means we need to increment the array ID and add the domain name. Once you have added a new one it should look something like below. Repeat this procedure for any new IP’s or domains you want Nextcloud to be able to operate through.

'trusted_domains' =>
array (
    0 => '192.168.1.105',
    1 => 'nextcloud.pimylifeup.com',
),

3. Now we can save and quit out of the file by pressing CTRL + X then pressing Y and then ENTER.

4. Finally you will need to port forward two ports to finally have Nextcloud up and running. These two ports being Port 80 and Port 443. The protocol required for these is TCP.

Hopefully by now you should have a fully operational Raspberry Pi Nextcloud Server.

If you come across any issues or have some feedback related to this tutorial, then please don’t hesitate to leave a comment below.

Comments

Popular posts from this blog

OWASP Top 10 Threats and Mitigations Exam - Single Select

Last updated 4 Aug 11 Course Title: OWASP Top 10 Threats and Mitigation Exam Questions - Single Select 1) Which of the following consequences is most likely to occur due to an injection attack? Spoofing Cross-site request forgery Denial of service   Correct Insecure direct object references 2) Your application is created using a language that does not support a clear distinction between code and data. Which vulnerability is most likely to occur in your application? Injection   Correct Insecure direct object references Failure to restrict URL access Insufficient transport layer protection 3) Which of the following scenarios is most likely to cause an injection attack? Unvalidated input is embedded in an instruction stream.   Correct Unvalidated input can be distinguished from valid instructions. A Web application does not validate a client’s access to a resource. A Web action performs an operation on behalf of the user without checking a shared sec

CKA Simulator Kubernetes 1.22

  https://killer.sh Pre Setup Once you've gained access to your terminal it might be wise to spend ~1 minute to setup your environment. You could set these: alias k = kubectl                         # will already be pre-configured export do = "--dry-run=client -o yaml"     # k get pod x $do export now = "--force --grace-period 0"   # k delete pod x $now Vim To make vim use 2 spaces for a tab edit ~/.vimrc to contain: set tabstop=2 set expandtab set shiftwidth=2 More setup suggestions are in the tips section .     Question 1 | Contexts Task weight: 1%   You have access to multiple clusters from your main terminal through kubectl contexts. Write all those context names into /opt/course/1/contexts . Next write a command to display the current context into /opt/course/1/context_default_kubectl.sh , the command should use kubectl . Finally write a second command doing the same thing into /opt/course/1/context_default_no_kubectl.sh , but without the use of k

标 题: 关于Daniel Guo 律师

发信人: q123452017 (水天一色), 信区: I140 标  题: 关于Daniel Guo 律师 关键字: Daniel Guo 发信站: BBS 未名空间站 (Thu Apr 26 02:11:35 2018, 美东) 这些是lz根据亲身经历在 Immigration版上发的帖以及一些关于Daniel Guo 律师的回 帖,希望大家不要被一些马甲帖广告帖所骗,慎重考虑选择律师。 WG 和Guo两家律师对比 1. fully refund的合约上的区别 wegreened家是case不过只要第二次没有file就可以fully refund。郭家是要两次case 没过才给refund,而且只要第二次pl draft好律师就可以不退任何律师费。 2. 回信速度 wegreened家一般24小时内回信。郭律师是在可以快速回复的时候才回复很快,对于需 要时间回复或者是不愿意给出确切答复的时候就回复的比较慢。 比如:lz问过郭律师他们律所在nsc区域最近eb1a的通过率,大家也知道nsc现在杀手如 云,但是郭律师过了两天只回复说让秘书update最近的case然后去网页上查,但是上面 并没有写明tsc还是nsc。 lz还问过郭律师关于准备ps (他要求的文件)的一些问题,模版上有的东西不是很清 楚,但是他一般就是把模版上的东西再copy一遍发过来。 3. 材料区别 (推荐信) 因为我只收到郭律师写的推荐信,所以可以比下两家推荐信 wegreened家推荐信写的比较长,而且每封推荐信会用不同的语气和风格,会包含lz写 的research summary里面的某个方面 郭家四封推荐信都是一个格式,一种语气,连地址,信的称呼都是一样的,怎么看四封 推荐信都是同一个人写出来的。套路基本都是第一段目的,第二段介绍推荐人,第三段 某篇或几篇文章的abstract,最后结论 4. 前期材料准备 wegreened家要按照他们的模版准备一个十几页的research summary。 郭律师在签约之前说的是只需要准备五页左右的summary,但是在lz签完约收到推荐信 ,郭律师又发来一个很长的ps要lz自己填,而且和pl的格式基本差不多。 总结下来,申请自己上心最重要。但是如果选律师,lz更倾向于wegreened,