From 67f0cc0a60da5785294ebfbfb05654a2580af816 Mon Sep 17 00:00:00 2001 From: Benjamin Staneck Date: Tue, 15 May 2018 21:30:35 +0200 Subject: [PATCH] Updated SSL (markdown) --- SSL.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/SSL.md b/SSL.md index 4273587..a32b0e5 100644 --- a/SSL.md +++ b/SSL.md @@ -47,19 +47,19 @@ Mono doesn't support intermediate certificates, which results in a broken chain 1. Using OpenSSL >1.0.0 it should be possible to generate a .pvk using a .pem from LetsEncrypt -openssl rsa -in privkey.pem -outform PVK -pvk-none -out sonarr.pvk +`openssl rsa -in privkey.pem -outform PVK -pvk-none -out yourdomain.pvk` 2. You will also need to generate a .cert from .pem -openssl x509 -inform PEM -in cert.pem -outform DER -out sonarr.cert +`openssl x509 -inform PEM -in cert.pem -outform DER -out yourdomain.cert` ### Synology Only _If you're not running Sonarr on a Synology, skip these steps_ 1. Place the SSL certificate **and** converted key in `pvk` format in `/volume1/@appstore/nzbdrone/var/` -2. Load the certificate with `httpcfg` (comes with mono) as `nzbdrone`, the user that runs Sonarr: +2. Load the certificate with `httpcfg` (comes with mono) as `sc-nzbdrone`, the user that runs Sonarr: - `su nzbdrone -c "/volume1/@appstore/mono/bin/httpcfg -add -port -pvk yourdomain.pvk -cert yourdomain.cert"` + `su sc-nzbdrone -c "/volume1/@appstore/mono/bin/httpcfg -add -port -pvk yourdomain.pvk -cert yourdomain.cert"` *Replace `` with the SSL port you set in Sonarr.* 3. Skip the importing step below as the pvk and cert have already been imported