Install Nextcloud on Synology NAS Diskstation DSM 6

Hopefully this method should cover most details needed for a basic installation of nextcloud on a synology diskstation dsm 6. If you know something that might be helpful don’t hesitate to tell me. Btw this tutorial should work for owncloud as well.

1. Install dependencies

Start by installing the packages needed through the DSM Package center

  • Web station
  • Apache HTTP Server 2.4
  • PHP 7.0
  • Phpmyadmin
  • MariaDB 10

2. Change default MariaDB password

  • Open MariaDB 10.
  • Click “Change MariaDB password”
    Standard password is blank so leave the first form blank and click “reset password”
  • Enter a strong password.
mariadb10

Virtual host or basic setup

Web Station has the ability to create virtual hosts which is handy if you want to point a specific domain to your nextcloud installation. Most people might just use their synology “quick connect” adress and place the nextcloud installation in the root of the web-folder like so: yourdsmname.synology.me/nextcloud
I have my own domain so I wanted to point it straight to my nextcloud installation. I will explain both setups in step 3.

3. (Basic setup – no virtual host).

  • Open Web Station
  • Go to General Settings and choose Apache 2.4 as back-end and Php 7.0 as PHP version.
Web Station Apache and PHP setup

3. (Alternative setup for using a virtual host).

  • Open Web Station
  • Go to Virtual Host and click “Create”
  • Enter your hostname: yourdomain.com
  • choose 80/443 for ports
  • For Document root: click browse and select the folder where you want to install nextcloud. If you choose /web/nextcloud you will be able to access your nextcloud installation both through your virtual hostname and through yourdsmname.synology.me/nextcloud
  • Choose Apache 2.4 for HTTP Back-end, and PHP 7.0 for PHP version.
5

Click OK and your virtual host is set up. The next steps are the same for both setups. Only thing to keep in mind is your chosen installation folder.

4. Configure PHP 7 extensions

Go to PHP Settings and select PHP 7.0 and Edit.

4
  • First select “Customise PHP open_basedir” This is so that you can customise where to put your nextcloud data-folder (where you will keep all your personal files). It’s a good idea to keep your data folder away from your nextcloud installation.
  • At the end of the open_basedir: type a semi colon and enter the path to your data folder (see image).
  • Next you will need to enable certain extensions for Nextcloud to work properly

These following are enabled on my server, I honestly don’t remember which ones where specifically needed for nextcloud. You might not need all of them but it shouldn’t hurt to have them enabled:

  • bz2
  • curl
  • gd
  • mysqli
  • openssl
  • pdo_mysql
  • zip

5. Edit PHP 7 Values

Open the “Core” tab and search for the followin values and change them accordingly

  • mysql.default_port=3307  (this is the default port for MariaDB 10)
  • opcache.enable=1
  • opcache.enable_cli=1
  • opcache.interned_strings_buffer=8
  • opcache.max_accelerated_files=10000
  • opcache.memory_consumption=128
  • opcache.save_comments=1
  • opcache.revalidate_freq=1

Now you have prepared an environment where nextcloud should work. The next steps are the actual installation steps.

6. Download the latest nextcloud

  • zip from here nextcloud.com/install
  • Place the nextcloud.zip in the root of your web folder (/volume1/web/) and unzip it there.

7. Fix permissions

  • Open a text editor and paste the following text.
#!/bin/bash

chown -R http:http /volume1/web/nextcloud/
chown -R http:http /volume1/web/nextcloud/apps/
chown -R http:http /volume1/web/nextcloud/config/
chown -R http:http /volume1/web/nextcloud/themes/
chown -R http:http /PATH/TO/DATAFOLDER/
chown http:http /volume1/web/nextcloud/.htaccess
find /volume1/web/nexctloud/ -type f -print0 | xargs -0 chmod 777
find /volume1/web/nextcloud/ -type d -print0 | xargs -0 chmod 777
find /PATH/TO/DATAFOLDER/ -type d -print0 | xargs -0 chmod 777
chmod 777 /volume1/web/nextcloud/.htaccess

Edit the paths to match your environment.

  • Save your script as permissions.sh and upload it to your synology nas.

    Run your permissions file
  • Log in to your server through SSH
    ssh admin@yourdsmhost.com
    (ip-adress works fine too)
    (if ssh is disabled you need to enable it first through the Control panel and in “Terminal & SNMP” select “Enable SSH service”
  • go to the directory where you saved you permissions.sh file
    cd /path/to/directory/
  • Run the file:
    sudo ./permissions.sh

    when prompted, type your admin password and press enter.

8. Configure Nextcloud

Now open your web browser and enter the adress of your nextcloud installation i.ex: yourdsmname.synology.me/nextcloud or yourdomain.com

If all is good you should find your self at the installation page for Nextcloud. If your page is blank or you get an error, make sure apache 2.4 and php 7 are selected in your web station/virtual host and not nginx.

6
9. Last step

Fill out the “form” according to your installation (see picture above)

  • choose a username and password for your first user (will be an administrator)
  • Enter the path to your datafolder (where you have chosen to keep your personal files)
  • choose MariaDB as database (can’t find mariadb? check the notes in the bottom)
  • enter the username and password that you chose earlier in step 2.
  • choose any name for the database, just no spaces or leave it for default.
  • enter 127.0.0.1:3307 as hostname to make sure nextcloud connects properly to MariaDB

Steps to consider after installation

Behind a firewall?

If you are behind a firewall, make sure to port forward at least port 80 to your synology dsm to give access to your Nextcloud installation. If you are planning on using https, you need to forward port 443 as well.

HTTPS with Let’s Encrypt

A good practice is to use https on any web site unless the access to your website is only on a local network. Synology has built in let’s encrypt which support great and free ssl certificates.

Create Let’s Encrypt certificate
go to control panel and security, certificate and click “add”.
For the domain name, either you can use your synology quick access name or you can use your own domain, just make sure your domain is pointing to your diskstation.
Unless you are using subdomains, just leave the “Subject Alternative Name:” blank.

Force HTTPS through .htaccess
Go to your nextcloud installation folder and edit config.php in the config folder. Find the overwrite.cli.url value and change the http to https.

'overwrite.cli.url' => 'https://yourdomain.com',

Problem Solving

Click to expand. Thanks everyone for contributing!

Nextcloud not working after update
If you updated your nextcloud installation you’ll need to fix your permissions again according to step 7

MariaDB not showing up on nextcloud install screen
If you can’t find MariaDB once you’ve arrived at the nextcloud installation screen, make sure that MariaDB is installed and that you have changed the PHP 7 value according to step 5 to 3307. If for some reason it refuses to save 3307 and defaults to 3306 (which is mariadb 5). Try to install MariaDB 5 as well. This might make it visible for nextcloud. You should still be able to choose 127.0.0.1:3307 for host, to force it to use MariaDB 10. If not, you might consider trying MariaBD 5.

Screen blank or error 503 or others.
I was shown several error pages during my trial and errors. Most of them where connected to Nginx, permissions or the PHP 7 -settings. Nginx is not used in this tutorial so if you get nginx errors, try changing any value where nginx is selected to apache 2.4 in web station. If it’s a permission problem, check the permissions.sh file and make sure it has the correct paths. Also make sure that “Customise PHP open_basedir” is correct according to step 4.

the PHP 7 -settings. Nginx is not used in this tutorial so if you get nginx errors, try changing any value where nginx is selected to apache 2.4 in web station. If it’s a permission problem, check the permissions.sh file and make sure it has the correct paths. Also make sure that “Customise PHP open_basedir” is correct according to step 4.

Various issues when updating
Thanks Philip for these!
All entered in an ssh terminal after issuing sudo -i:

To update missing indexes enter this command, substituting your php.id in place of my semi-hidden one:

sudo -u http /usr/local/bin/php70 -c /var/packages/WebStation/etc/php_profile/9f1e642a-0d20-4664-8934-cxxxxxxxxxe/conf.d/user_settings.ini -f /volume1/web/nextcloud/occ db:add-missing-indices

sudo -u http /usr/local/bin/php70 -c /var/packages/WebStation/etc/php_profile/9f1e642a-0d20-4664-8934-cxxxxxxxxxee/conf.d/user_settings.ini -f /volume1/web/nextcloud/occ db:convert-filecache-bigint

The php profile id is unique to each installation

To update Strict-Transport-Security:
echo ‘add_header Strict-Transport-Security “max-age=31536000; includeSubDomains” always;’ > /etc/nginx/conf.d/http.hsts.conf

To update caching:
edit /volume1/web/nextcloud/config/config.php and add:
‘memcache.local’ => ‘\\OC\\Memcache\\APCu’,

To solve ocs and ocm provider errors:
ln -s /var/services/web/nextcloud/ocm-provider/ /var/services/web
ln -s /var/services/web/nextcloud/ocs-provider/ /var/services/web

The last solution took me hours and hours to solve, but was so simple! I had been trying to link using /volume1/web but for some reason it required the ‘real’ location of /var/services/web

max file size below 512MB
In DSM, go to WebStation then PHP settings. Make sure you have PHP version 7.2 showing – if not go to package manager and install it and make it default in PHP settings. Double click ‘Default profile PHP 7.2’, go to ‘Core’ and find ‘memory_limit’. Set it to 512M.

There were a few warnings in Nextcloud/Overview of various tables not being updated correctly. The command I used to sort these out was:

sudo -u http /usr/local/bin/php72 -c /var/packages/WebStation/etc/php_profile/9f1e642a-0d20-4664-8934-xxxxxxxxxxxx/conf.d/user_settings.ini -f /volume1/web/nextcloud/occ db:add-missing-indices

The string starting with 9f1e is my PHP id. You will need to substitute your own – have a look in /var/packages/WebStation/etc/php_profile/ to find it. There were a couple there for me, so I tried both to find the one which worked.

I got a couple of mcrypt errors, but the command ran successfully and created everything it needed to.

Nextcloud/Overview also complained about Intl being a fallback version, I just went back to DSM and in WebStation/PHP settings/Default profile PHP 7.2 I saw I hadn’t enabled Intl. Once done the NextCloud error went away.

40 Comments

  1. I want to change the default ports 80, 443 to 880 and 4443 since I am already port forwarding 80 internally for a media server and 443 for a VPN server.

    The question is what are the config files that I would have to do this with? Apache? PHP?

    Any guides or references on this would be appreciated.

    • Hi GB, sorry for my late reply. I would set it up using virtual hosts as explained in step 3. If you need to use a different port (which you most likely wont if you just set it up to use virtual host) instead of clicking the default port 80, choose your own ports right below for both http and https. That should do the trick.

    • Thanks Evie. That’s probably the most random and nicest comment yet, it certainly makes me want to write a part 2, what should it be about? =)

  2. I get pleasure from, result in I found just what I was taking
    a look for. You have ended my 4 day lengthy hunt! God Bless you man. Have
    a great day. Bye

  3. Hi David
    great guideline for the nextcloud installation. I am facing two problems:
    1.) I have already in the Webstation my webpage configured. When I want to add a new virtual host for nextcloud it does not allow me to use the host name
    2.) Using PHP 7 I can’t set the extensions under PHP settings. Possibility to do so is not displayed. FYI: I am using DSM 6.1.7

    • Hey Michael, sorry for the late reply.
      1. Nextcloud doesn’t really “care” which hostnames you use. You set the www root directory for the new hostname in webstation. After that make sure that the nextcloud folder is in that directory. That should be enough.
      2. This I have no clue about I’m afraid. Can you ta a screenshot and link to it so I can see what the settings look like?

  4. Greetings! Quick question that’s totally off topic.

    Do you know how to make your site mobile friendly?
    My weblog looks weird when viewing from my iphone. I’m trying to
    find a theme or plugin that might be able to correct this issue.
    If you have any recommendations, please share. Cheers!

    • Hi Brenna. Not sure I’m going to be a good help for you. There are a few different ways to do this. There are plugins that let your site detect if your visitors are using a mobile device and can “redirect” them to a special theme made for a mobile devices. That’s how most people used to do it. Today the most common way is just to look for a responsive theme that you like, which means that the page will resize itself depending on the size of the screen. But they can look “weird” if you have lots of content that doesn’t work with smaller screens. You can also choose to not display certain elements depending on the screen size by setting css rules. I don’t know if that helps. Cheers!

  5. Hi,
    Thanks you very much for your tutorial. With your help, I succeeded to install Nextcloud 13 on my NAS Synology 713+.
    After I custumized my config/config.php file, Nextcloud displayed an error message : impossible to use it. But after I used again the permissions.sh script, the problem disappeared.
    Regards,

    Thierry

  6. Hi,

    Thanks for this great guideline ! I’m kind of new on this, but I’m nearly at the end of it, but…

    when I run the permissions.sh file I got theses errors :

    admin@NAS:~$ sudo /volume1/COMMUN/permissions.sh
    Password:
    /volume1/COMMUN/permissions.sh: line 1: {rtf1ansiansicpg1252cocoartf1504cocoasubrtf830: command not found
    /volume1/COMMUN/permissions.sh: line 2: syntax error near unexpected token `}’
    /volume1/COMMUN/permissions.sh: line 2: `{\fonttbl\f0\fmodern\fcharset0 Courier;}’

    I 100% sure that I missed something since I’m a total beginer.. Does theses errors can help you to point me my mistake ?

    Thanks in advance for your help !

    Cheers

    Eric

  7. Hi,
    Really like the blog.
    However, I don’t seem to get it working.
    When using my internal ip:
    192.168.1.XX/nextcloud
    I get the screen and everything seems to work (although I didn’t test to much).

    when I use
    xxxx.quickconnect.to/nextcloud
    I always get redirected to xxx.quickconnect.to something like
    https://xxxxx.fr2.quickconnect.to/nextcloud
    which doesn’t exist.

    If i use xxxx.quickconnect.to/nextcloud on my lan (where the nas is)
    I get redirected to
    192.168.1.XX:5001/nextcloud

    Any idea what I should check?

  8. Hi, It looks like you might have gotten a few random characters and line breaks in the permissions.sh file. Maybe copying the text from the browser didn’t work correctly. Send me a pm through the contact page or chat bubble and I can send you the file as a zip. It should work.

  9. I think the problem might be related to quickconnect. I rarely use it since it rarely works for anything except connecting to the DSM. I would try using DDNS in the control panel > external access > DDNS and add a xxxxx.synology.me domain. Then try connecting to xxxxx.synology.me/nextcloud and see if that works.
    Regarding your lan there could be multiple reasons for this. Have you set up a virtualhost? if so you could add that virtual host to your /etc/hosts file on your computer if it’s linux/osx or you might be able to add it to your router depending on model. That way, you override any DNS queries and point it straight to your NAS. If you use Virtual host and want external access you would need to register that domain some where and you might need to enable nat loopback on your router if it doesn’t work. I don’t know if any of that helps, don’t hesitate to ask again or if I was unclear.

  10. Thank you so much for this. I now have a fully working Nextcloud installation on my Synology DS218+. I now want to make sure everything is backed up. I use Hyperbackup to backup the whole web folder, and another to backup the app MariaDB. Am I doing enough to ensure my calendar and contacts are backed up? I’ve been searching so much online, but all I have found are instructions to backup a Linux based Nextcloud installation. I can’t adapt the instructions for a Synology install.

    Any advice would be gratefully received!

    Thank you.

    • I’m glad you found it helpful! Yes the web folder (and volume folder if placed somewhere else) and database is enough for backing up your installation. Just make sure to backup any encryption keys you have separately as well if you decide to use encryption on nextcloud, those won’t get backed up in the database. Other wise you should be good!

    • Hi,

      You just have to change the Customise PHP open_basedir (step 4) to the directory you want to store your files in. For example /volume2/nextcloud/

      You also have to edit the permissions.sh file with your path. So if we take /volume2/nextcloud/ as an example again:
      chown -R http:http /PATH/TO/DATAFOLDER/ –>
      chown -R http:http /volume2/nextcloud/

      and

      find /PATH/TO/DATAFOLDER/ -type d -print0 | xargs -0 chmod 777 –>
      find /volume2/nextcloud/ -type d -print0 | xargs -0 chmod 777

      Now if you try to go to the /volume2/nextcloud/ directory in DSM you might get an error that you don’t have permissions for accessing it. Right click the directory, go to Properties and then Permission. Click create and add your account. There are a lot of resources online if you have troubles with changing the permissions of the directory. Just search for dsm permissions or something.

  11. The problem I’m having is that when there’s an issue nothing online seems to address the problem when it has to do with a Diskstation installation. I just upgraded to NextCloud 15.0.5 and got these errors, one for ocm-provider and another for ocs-provider:

    Your web server is not properly set up to resolve “/ocm-provider/”. This is most likely related to a web server configuration that was not updated to deliver this folder directly. Please compare your configuration against the shipped rewrite rules in “.htaccess” for Apache or the provided one in the documentation for Nginx at it’s documentation page. On Nginx those are typically the lines starting with “location ~” that need an update.

    I’ve gone through all the config files I can find and the only one remotely to do with the error says explicitly not to change anything above this line – and the line is right at the end of the file, lol!

    Any ideas?

    Thank you!

  12. Hi,
    i have the same issue.
    I seems liked to the fact that nextcloud is installed in a subfolder. As my nextcloud instance is installed in a subfolder named nextcloud, I resolve the issue with the following lines in my virtual host (running under Apache).
    RedirectPermanent /ocm-provider /nextcloud/ocm-provider
    RedirectPermanent /ocs-provider /nextcloud/ocs-provider

  13. Hi, (sorry, the same message without typos)
    I have the same issue.
    It seems to be linked to the fact that nextcloud is installed in a subfolder. As my nextcloud instance is installed in a subfolder named nextcloud, I resolve the issue with the following lines in my virtual host (running under Apache).
    RedirectPermanent /ocm-provider /nextcloud/ocm-provider
    RedirectPermanent /ocs-provider /nextcloud/ocs-provider

  14. Interesting. I don’t run a virtual host – just a Synology DS218+ connected normally to the internet. The problem is there are plenty of solutions like yours but I have no idea where to put the comments suggested since the implementation of Nextcloud on a Synology NAS is rather different than on full Linux. None of the suggested configuration files seem to exist.

  15. Hi Everyone
    Just a notice. Since updates, be them either Nextcloud or DSM, seem to break the Nextcloud installation in different ways for many, there is a “workaraound” that I’ve tried myself which is to install Synology’s Virtual Machine Manager. It’s not available for most DSM’s but is manually installable if you have a x86 DSM from here https://usdl.synology.com/download/Package/spk/Virtualization/ Download the latest version in the list and manually install it. After that you can install any flavor of Linux, I installed Ubuntu Server. Ubuntu server even has the option to install Nextcloud out of box and it just works. I can write a tutorial for it if anyone requests it.
    Thanks everyone for keeping this page alive.

  16. I’ve just looked at VMM and it is very limited – not only in relation to the NAS hardware but it also needs to be running BTRFS. What about using Docker? This seems to be much more accessible.

    • I tried installing Nextcloud as Docker image – it all worked within my local network but I just couldn’t access it from outside. I think the problem may have been that my normally installed version of Nextcloud was still running. I don’t want to delete that just to try Docker. Since it’s all working apart from the OCS and OCM error messages I’ll stick with it. It appears the issue is affecting those who have a completely conventional Linux installation too so it’s a bigger problem that for those of us who have Nextcloud installed on out Diskstations.

      • Thanks Philip for testing this out. I haven’t had time to do much testing lately (recently became the father of twins =)). I’ve been thinking about docker as well but there seemed to be other issues people ran into with the docker images so I discarded the idea at first, but maybe I’ll give it a go and see if I can get it running more fluidly. The Vm is working flawlessly for now but the problem is that the VM’s can’t share storage with DSM which is kind of dumb imo, you are correct that VMM is quite limited.. However very simple to setup.

        • Congratulations on the twins David! You’ll certainly be very busy with them! Would be good if you could lend your expertise to a step-by-step Docker install of Nextcloud on a Synology NAS . . .

  17. OK. Some solutions to various issues which occur when updating a standard installation of Nextcloud on a Synology NAS. All entered in an ssh terminal after issuing sudo -i:

    To update missing indexes enter this command, substituting your php.id in place of my semi-hidden one:

    sudo -u http /usr/local/bin/php70 -c /var/packages/WebStation/etc/php_profile/9f1e642a-0d20-4664-8934-cxxxxxxxxxe/conf.d/user_settings.ini -f /volume1/web/nextcloud/occ db:add-missing-indices

    sudo -u http /usr/local/bin/php70 -c /var/packages/WebStation/etc/php_profile/9f1e642a-0d20-4664-8934-cxxxxxxxxxee/conf.d/user_settings.ini -f /volume1/web/nextcloud/occ db:convert-filecache-bigint

    The php profile id is unique to each installation

    To update Strict-Transport-Security:

    echo ‘add_header Strict-Transport-Security “max-age=31536000; includeSubDomains” always;’ > /etc/nginx/conf.d/http.hsts.conf

    To update caching:

    edit /volume1/web/nextcloud/config/config.php and add:
    ‘memcache.local’ => ‘\\OC\\Memcache\\APCu’,

    To solve ocs and ocm provider errors:

    ln -s /var/services/web/nextcloud/ocm-provider/ /var/services/web
    ln -s /var/services/web/nextcloud/ocs-provider/ /var/services/web

    The last solution took me hours and hours to solve, but was so simple! I had been trying to link using /volume1/web but for some reason it required the ‘real’ location of /var/services/web

    Hope this helps someone!

    • I upgraded to NextCloud v16 today so thought I’d post some more solutions. After the upgrade I had some errors showing up in Nextcloud/Overview.

      It said the max file size was below 512MB – that was easy. In DSM, go to WebStation then PHP settings. Make sure you have PHP version 7.2 showing – if not go to package manager and install it and make it default in PHP settings. Double click ‘Default profile PHP 7.2’, go to ‘Core’ and find ‘memory_limit’. Set it to 512M.

      There were a few warnings in Nextcloud/Overview of various tables not being updated correctly. The command I used to sort these out was:

      sudo -u http /usr/local/bin/php72 -c /var/packages/WebStation/etc/php_profile/9f1e642a-0d20-4664-8934-xxxxxxxxxxxx/conf.d/user_settings.ini -f /volume1/web/nextcloud/occ db:add-missing-indices

      The string starting with 9f1e is my PHP id. You will need to substitute your own – have a look in /var/packages/WebStation/etc/php_profile/ to find it. There were a couple there for me, so I tried both to find the one which worked.

      I got a couple of mcrypt errors, but the command ran successfully and created everything it needed to.

      Nextcloud/Overview also complained about Intl being a fallback version, I just went back to DSM and in WebStation/PHP settings/Default profile PHP 7.2 I saw I hadn’t enabled Intl. Once done the NextCloud error went away.

      Hope this helps someone.

      • Thanks again bro! Btw I’ve been labbing with several different installations of nextcloud lately to see which one turns out to be the most reliable (especially when it comes to updates) on a/my Synology NAS. Once I’m happy with the outcome (and have time to write it) I’ll post a new tutorial for it so stay tuned =)

  18. Hi, thanks for the guide. I installed Nextcloud without any errors but I’m not able to reach the Cloud outside of the LAN or with the mobile app. Could you help me? I set up the DynDDNS with Synology, added the Lets encrypt certificate, enabled port forwarding in my router and edited the config.php with the dynddns Hostname. Did I miss something? What exacly do I have to put in as the address to find the cloud from outside?

    Cheers,

    Gottlob

    • Are you using a virtual host? If you have not set up a virtual host, adding a domain name and pointing it to your nas simply adds an additional adress to your nas. Let’s say your nas is nasdomain.com, then your nextcloud install should be in nasdomain.com/nextcloud (if you have named the folder in the base of your www-folder nextcloud) If you add a new domain and point it to your nas as well i.ex nascloud.com then the adress will simply be nascloud.com/nextcloud. But if you have added a virtual host and pointed that host to your nextcloud folder, you should be able to access nextcloud by navigating to the domain directly. I hope this helps.

      • Thanks for the quick reply David.. The problem was with my ISP. I had a DS-Lite connection, so no public IPv4 address. I got that fixed, so it should work, but I have another problem. Now when I want to connect via my the nextcloudapp on my phone it says untrusted domain. But I added my NAS domain in the config file of nextcloud so I’m a bit confused now why it doesnt work :/ I also added the Lets encrypt certificate. I read something about changing something in the apache config file but I’m not sure. Something about a redirecting something. Do you know anything about that problem?

        Thanks in advance.

        • I’m glad you got the first part figured out! Hm.. untrusted definitely sounds like it has to do with ssl. Are you entering https://domain or just the domain when you connect through the app? Also when you connect through a normal browser, does the browser show that you are connected with https with a working ssl certificate from let’s encrypt? If the browser can connect and the ssl certificate is working, I can’t see why the app couldn’t unless you aren’t using ssl to connect. The app doesn’t necessarily know ssl is supposed to be used unless you enter it in the adress (https://domain). You can also make sure nextcloud redirect all traffic to https (Not sure if that helps the app though). There are a few ways to do it, I usually just use mod rewrite in .htaccess. There are tons of guides, just shout if you need any help. That’s all I can think of from the top of my mind. Hope something helps. Please post your solution, it might help someone else.

  19. Thank s for this great tutorial !
    I succeeded to install Nextcloud 16 on my NAS Synology 916+
    I have just a little issue with Nextcloud Android client. It can’t connect to the server:
    ‘fail to initialise SSL’ (ok for iPhone).
    Do you know anything about this. ?

1 Trackback / Pingback

  1. Install Nextcloud on Synology NAS Diskstation DSM 6 – with Docker – luvis.se

Leave a Reply to Phillip Deackes Cancel reply

Your email address will not be published.


*


This site uses Akismet to reduce spam. Learn how your comment data is processed.