Nextcloud is by far the best (and in many ways only) free and open source cloud storage solution. Not only can the client be used on nearly all platforms such as desktop, android and IOS but it also doesn't take up much memory on your server.
-
-
-
You'll need a server or VPS running a Debian-based OS (Ubuntu 20 or Debian 10 are recommended) and at least 512MB of RAM. You'll also need a domain name pointing to your server's IP address.
-
-
-
- Note that although you can use NGINX instead of Apache (and I've successfully done it before) it's not officially supported.
- More info here.
-
-Next run the mysql_secure_installation using the below command
-
-
-
-mysql_secure_installation
-
-
-
-Next run mariadb and enter the below SQL commands.
-
-
-
-CREATE DATABASE nextcloud;
-CREATE USER nextcloud IDENTIFIED BY 'ENTER A SECURE PASSWORD';
-GRANT USAGE ON *.* TO 'nextcloud'@'localhost' IDENTIFIED BY 'YOUR PASSWORD';
-GRANT ALL privileges ON nextcloud.* TO 'nextcloud'@'localhost';
-FLUSH PRIVILEGES;
-
-Next we'll create an SSL certificate for your domain name. For tutorial purposes I'll use the domain nextcloud.example.com. Thanks to the EFF anyone can get an SSL certificate for free using Certbot.
-First we'll install the dependancies:
-
-
-
-apt install certbot python3-certbot-apache
-
-
-
-Next you'll need to go to the file /etc/apache2/sites-available/000-default.conf and change the section in ServerName from example.com to whatever your domain is.
-Then you can copy this file to the sites enabled with the below commands:
-
-Next run the below command to create your cert:
-
-
-
-certbot --apache -d $my_domain --redirect
-
-
-
Housekeeping and security best practices
-
-The remaining commands are just to make your server work/secure it as much as possible.
-First we'll need to create the directory for storing the data. We're doing it in the root directory so there's no chance of someone accessing it from the browser.
-
-Next go to the /etc/php/7.3/apache2/php.ini and make the following changes.
-
-
-
-Change upload_max_filesize = 2M to 512M
-
-
Change memory_limit = 128M to 512M
-
-
Change post_max_size = 8M to 512M
-
-
-
-Next go to the /etc/apache2/sites-enabled/000-default-le-ssl.conf file and add the following to it:
-NOTE: Remove the space at the start of the IfModule and VirtualHost tags I only added it in because html makes it disappear.
-
-
-
-
-
diff --git a/nextcloud_nginx.html b/nextcloud_nginx.html
new file mode 100644
index 0000000..ed6a3be
--- /dev/null
+++ b/nextcloud_nginx.html
@@ -0,0 +1,344 @@
+
+
+
+ Nextcloud Server with Nginx– LandChad.net
+
+
+
+
+
+
+
+
Nextcloud Server using Nginx
+
+
+
+
Nextcloud is by far the best (and in many ways only) free and open source cloud storage solution. Not only can the client be used on nearly all platforms such as desktop, android and IOS but it also doesn't take up much memory on your server.
+
+
+
You'll need a server or VPS running a Debian-based OS (Ubuntu 20 or Debian 10 are recommended) and at least 512MB of RAM. You'll also need a domain name pointing to your server's IP address.
+
+
+
+ Note that although I am using Nginx it's not officially supported.
+ More info here.
+
+Enable and start the nginx systemD service with the below command:
+
+
+
systemctl start nginx
+systemctl enable nginx
+
+
+
+Next run the mysql_secure_installation using the below command
+
+
+
+mysql_secure_installation
+
+
+
+Next run mariadb and enter the below SQL commands.
+
+
+
+CREATE DATABASE nextcloud;
+CREATE USER nextcloud IDENTIFIED BY 'ENTER A SECURE PASSWORD';
+GRANT USAGE ON *.* TO 'nextcloud'@'localhost' IDENTIFIED BY 'YOUR PASSWORD';
+GRANT ALL privileges ON nextcloud.* TO 'nextcloud'@'localhost';
+FLUSH PRIVILEGES;
+
+Next we'll create an SSL certificate for your domain name. For tutorial purposes I'll use the domain nextcloud.example.com. Thanks to the EFF anyone can get an SSL certificate for free using Certbot.
+First we'll install the dependancies:
+
+
+
+apt install certbot
+
+
+
+Next you'll need to go to the file /etc/nginx/sites-available/default and change the section in ServerName from example.com to whatever your domain is.
+Then you can copy this file to the sites enabled with the below commands:
+
+Next run the below command to create your cert:
+
+
+
+certbot -d $my_domain --redirect
+
+
+
Housekeeping and security best practices
+
+The remaining commands are just to make your server work/secure it as much as possible.
+First we'll need to create the directory for storing the data. We're doing it in the root directory so there's no chance of someone accessing it from the browser.
+
+Next go to the /etc/php/7.3/nginx/php.ini and make the following changes.
+
+
+
+Change upload_max_filesize = 2M to 512M
+
+
Change memory_limit = 128M to 512M
+
+
Change post_max_size = 8M to 512M
+
+
+
+Next go to the /etc/nginx/sites-enabled/default file and add the following to it:
+NOTE: You'll need to change the cloud.example.com in all places in the below to your domain.
+
+
+
+server {
+ listen 443 ssl http2;
+ listen [::]:443 ssl http2;
+ server_name cloud.example.com;
+
+ # Use Mozilla's guidelines for SSL/TLS settings
+ # https://mozilla.github.io/server-side-tls/ssl-config-generator/
+ ssl_certificate /etc/ssl/nginx/cloud.example.com.crt;
+ ssl_certificate_key /etc/ssl/nginx/cloud.example.com.key;
+
+ # HSTS settings
+ # WARNING: Only add the preload option once you read about
+ # the consequences in https://hstspreload.org/. This option
+ # will add the domain to a hardcoded list that is shipped
+ # in all major browsers and getting removed from this list
+ # could take several months.
+ #add_header Strict-Transport-Security "max-age=15768000; includeSubDomains; preload;" always;
+
+ # set max upload size
+ client_max_body_size 512M;
+ fastcgi_buffers 64 4K;
+
+ # Enable gzip but do not remove ETag headers
+ gzip on;
+ gzip_vary on;
+ gzip_comp_level 4;
+ gzip_min_length 256;
+ gzip_proxied expired no-cache no-store private no_last_modified no_etag auth;
+ gzip_types application/atom+xml application/javascript application/json application/ld+json application/manifest+json application/rss+xml application/vnd.geo+json application/vnd.ms-fontobject application/x-font-ttf application/x-web-app-manifest+json application/xhtml+xml application/xml font/opentype image/bmp image/svg+xml image/x-icon text/cache-manifest text/css text/plain text/vcard text/vnd.rim.location.xloc text/vtt text/x-component text/x-cross-domain-policy;
+
+ # Pagespeed is not supported by Nextcloud, so if your server is built
+ # with the `ngx_pagespeed` module, uncomment this line to disable it.
+ #pagespeed off;
+
+ # HTTP response headers borrowed from Nextcloud `.htaccess`
+ add_header Referrer-Policy "no-referrer" always;
+ add_header X-Content-Type-Options "nosniff" always;
+ add_header X-Download-Options "noopen" always;
+ add_header X-Frame-Options "SAMEORIGIN" always;
+ add_header X-Permitted-Cross-Domain-Policies "none" always;
+ add_header X-Robots-Tag "none" always;
+ add_header X-XSS-Protection "1; mode=block" always;
+
+ # Remove X-Powered-By, which is an information leak
+ fastcgi_hide_header X-Powered-By;
+
+ # Path to the root of your installation
+ root /var/www/nextcloud;
+
+ # Specify how to handle directories -- specifying `/index.php$request_uri`
+ # here as the fallback means that Nginx always exhibits the desired behaviour
+ # when a client requests a path that corresponds to a directory that exists
+ # on the server. In particular, if that directory contains an index.php file,
+ # that file is correctly served; if it doesn't, then the request is passed to
+ # the front-end controller. This consistent behaviour means that we don't need
+ # to specify custom rules for certain paths (e.g. images and other assets,
+ # `/updater`, `/ocm-provider`, `/ocs-provider`), and thus
+ # `try_files $uri $uri/ /index.php$request_uri`
+ # always provides the desired behaviour.
+ index index.php index.html /index.php$request_uri;
+
+ # Rule borrowed from `.htaccess` to handle Microsoft DAV clients
+ location = / {
+ if ( $http_user_agent ~ ^DavClnt ) {
+ return 302 /remote.php/webdav/$is_args$args;
+ }
+ }
+
+ location = /robots.txt {
+ allow all;
+ log_not_found off;
+ access_log off;
+ }
+
+ # Make a regex exception for `/.well-known` so that clients can still
+ # access it despite the existence of the regex rule
+ # `location ~ /(\.|autotest|...)` which would otherwise handle requests
+ # for `/.well-known`.
+ location ^~ /.well-known {
+ # The rules in this block are an adaptation of the rules
+ # in `.htaccess` that concern `/.well-known`.
+
+ location = /.well-known/carddav { return 301 /remote.php/dav/; }
+ location = /.well-known/caldav { return 301 /remote.php/dav/; }
+
+ location /.well-known/acme-challenge { try_files $uri $uri/ =404; }
+ location /.well-known/pki-validation { try_files $uri $uri/ =404; }
+
+ # Let Nextcloud's API for `/.well-known` URIs handle all other
+ # requests by passing them to the front-end controller.
+ return 301 /index.php$request_uri;
+ }
+
+ # Rules borrowed from `.htaccess` to hide certain paths from clients
+ location ~ ^/(?:build|tests|config|lib|3rdparty|templates|data)(?:$|/) { return 404; }
+ location ~ ^/(?:\.|autotest|occ|issue|indie|db_|console) { return 404; }
+
+ # Ensure this block, which passes PHP files to the PHP process, is above the blocks
+ # which handle static assets (as seen below). If this block is not declared first,
+ # then Nginx will encounter an infinite rewriting loop when it prepends `/index.php`
+ # to the URI, resulting in a HTTP 500 error response.
+ location ~ \.php(?:$|/) {
+ fastcgi_split_path_info ^(.+?\.php)(/.*)$;
+ set $path_info $fastcgi_path_info;
+
+ try_files $fastcgi_script_name =404;
+
+ include fastcgi_params;
+ fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
+ fastcgi_param PATH_INFO $path_info;
+ fastcgi_param HTTPS on;
+
+ fastcgi_param modHeadersAvailable true; # Avoid sending the security headers twice
+ fastcgi_param front_controller_active true; # Enable pretty urls
+ fastcgi_pass php-handler;
+
+ fastcgi_intercept_errors on;
+ fastcgi_request_buffering off;
+ }
+
+ location ~ \.(?:css|js|svg|gif)$ {
+ try_files $uri /index.php$request_uri;
+ expires 6M; # Cache-Control policy borrowed from `.htaccess`
+ access_log off; # Optional: Don't log access to assets
+ }
+
+ location ~ \.woff2?$ {
+ try_files $uri /index.php$request_uri;
+ expires 7d; # Cache-Control policy borrowed from `.htaccess`
+ access_log off; # Optional: Don't log access to assets
+ }
+
+ # Rule borrowed from `.htaccess`
+ location /remote {
+ return 301 /remote.php$request_uri;
+ }
+
+ location / {
+ try_files $uri $uri/ /index.php$request_uri;
+ }
+}
+
+
+
+
+Then run the below commands and you should be all set:
+