Synology NAS Guide
Clone this wiki locally
Since Synology introduced Let's Encrypt, many of us benefit from free SSL.
On the other hand, many of us don't want to expose port 80/443 to the Internet, including opening ports on the router. The alternative is to use the DNS-01 protocol. Sadly the Synology implementation of Let's Encrypt currently (1-Jan-2017) only supports the HTTP-01 method which requires exposing port 80 to the Internet. Also, if the domain of your NAS has an IPv6 AAAA record set, the Synology implementation of Let's Encrypt will fail.
But we can access the NAS via SSH and configure it to renew certs instead of using the web dashboard.
With the Synology DSM deployhook included in 2.8.6, it is no longer required to run acme.sh on your Synology device to rotate the certificate. acme.sh just needs to be run on something that has access to the DSM's administrative interface. Additionally, the previous deployment methods can be drastically simplified with the following instructions.
$ sudo su $ cd ~ $ wget https://github.com/acmesh-official/acme.sh/archive/master.tar.gz $ tar xvf master.tar.gz $ cd acme.sh-master/ $ ./acme.sh --install --nocron --home /usr/local/share/acme.sh --accountemail "email@gmailcom" $ source ~/.profile
For CloudFlare, we will set two environment variables that acme.sh (specifically, the
dns_cf script from the
dnsapi subdirectory) will read to set the DNS record. You can get your CloudFlare API key here.
export CF_Key="MY_SECRET_KEY_SUCH_SECRET" export CF_Email="email@example.com"
If you generated an API Token, instead of using your global account key, set CF_Token instead.
export CF_Token="MY_SECRET_TOKEN_SUCH_SECRET" export CF_Email="firstname.lastname@example.org"
In case you use another DNS service, check the
dnsapi directory. Instructions for many DNS providers are already included. You can also find instructions on how to add another DNS service there, although that requires some software development skills.
Now it's time to create the certificate for your domain:
$ cd /usr/local/share/acme.sh $ export CERT_DOMAIN="your-domain.tld" $ export CERT_DNS="dns_cf" $ ./acme.sh --issue --home . -d "$CERT_DOMAIN" --dns "$CERT_DNS"
We will use the Synology DSM deployhook to deploy our certificate. This will override the default certificate, in the next section you can see how to create new certificates to be used for other services.
$ cd /usr/local/share/acme.sh # Single quotes prevents some escaping issues if your password or username contains certain special characters $ export SYNO_Username='Admin_Username' $ export SYNO_Password='Admin_Password!123' # You must specify SYNO_Certificate, for the default certificate, we use an empty string # Please be aware that the empty string only works if you haven't added/changed the description for # the default certificate. If you have, you'll need to specify the description here. $ export SYNO_Certificate="" $ ./acme.sh --deploy --home . -d "$CERT_DOMAIN" --deploy-hook synology_dsm
Note that if the user entered for
SYNO_Username has enabled two-factor authentication (2FA), the login will fail and the error states that user/password is wrong, even if both are correct.
To fix this, simply follow the steps described at the Synology DSM deployhook wiki page - in short: log into your DSM via its website, making sure you've ticked
Remember this device when asked for your OTP, get the
did cookie's value and set the environment variable:
export SYNO_DID='YOUR VALUE'
When we want to use https to deploy the new certificate and connect to "localhost", we need to add the --insecure option to the deploy command to prevent curl errors. refer to [https://github.com/acmesh-official/acme.sh/wiki/Options-and-Params]. If you enabled HTTP/2 you still receive a curl 16 error probably due to missing http2 dependencies on the NAS but the script succeeds.
$ cd /usr/local/share/acme.sh # Single quotes prevents some escaping issues if your password or username contains certain special characters $ export SYNO_Username='Admin_Username' $ export SYNO_Password='Admin_Password!123' # export SYNO_Hostname="localhost" # Specify if not using on localhost $ export SYNO_Scheme="https" $ export SYNO_Port="5001" # You must specify SYNO_Certificate, for the default certificate, we use an empty string # Please be aware that the empty string only works if you haven't added/changed the description for # the default certificate. If you have, you'll need to specify the description here. $ export SYNO_Certificate="" $ ./acme.sh --deploy --insecure --home . -d "$CERT_DOMAIN" --deploy-hook synology_dsm
By specifying a different
SYNO_Certificate and (optionally)
SYNO_Create, we can deploy multiple certificates to the DSM. These commands assume you are still working in the same terminal and have exported all other necessary variables described above.
$ ./acme.sh --issue --home . -d "subdomain.$CERT_DOMAIN" --dns "$CERT_DNS" # SYNO_Certificate is the description shown under Security -> Certificates in the DSM Control Panel $ export SYNO_Certificate="A different certificate" $ export SYNO_Create=1 # Says to create the certificate if it doesn't exist $ ./acme.sh --deploy --home . -d "subdomain.$CERT_DOMAIN" --deploy-hook synology_dsm
To auto renew the certificates in the future, you need to configure a task in the task scheduler. It is not advised to set this up as a custom cronjob (as was previously described in this wiki page) as the DSM security advisor will tell you that you have a critical warning regarding unknown cronjob(s).
In DSM control panel, open the 'Task Scheduler' and create a new scheduled task for a user-defined script.
- General Setting: Task - Update default Cert. User - root
- Schedule: Setup a weekly renewal. For example, 11:00 am every saturday.
- Task setting: User-defined-script:
# renew certificates /usr/local/share/acme.sh/acme.sh --cron --home /usr/local/share/acme.sh/
$ cd /usr/local/share/acme.sh $ ./acme.sh --force --upgrade --nocron --home /usr/local/share/acme.sh
or manually add below line into /root/.profile