Synology Docker Radarr, Sabnzbd, Plex

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g., so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:

It produced this output:

My web server is (include version): Radarr

The operating system my web server runs on is (include version): Synology DSM 6.2.3-25426 Update 3

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know): Yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): DSM

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

Experienced user, but new to SSL, beyond having my webhost set it up for me.

I have a No-ip name that successfully connects to my Plex, Radarr and Sabnzbd apps running in Docker on my Synology. Got everything forwarded through my router and Docker, and I've tested them unencrypted, and they work fine.

I've been searching around to find the most straightforward way to encrypt the connection. I found a post in this forum Synology DDNS Setup - #4 by tkeller that gives simple steps, Synology Control Panel - Security - Certificate - Add to add a Let's Encrypt certificate. That appears to have completed successfully.

At this point, I don't know where to find the certificate file and password/key that the apps need to actually use the certificate. I've been searching around a little, but I haven't found the thread that helps me with this. I don't see anything in the DSM Control Panel page where I created the certificate that tells me that info.

Hopefully, someone here has the info handy.


I managed to find a workaround to my own question.

In the Radarr Discord, I stumbled on a message stating that almost nobody is using the internal SSL code in each app. In fact, there was disagreement whether it was even being maintained and tested, regularly. They said everyone is using a Reverse Proxy.

About the same time, I happened to find this page Synology: How to Allow Plex to Work Over an HTTPS Connection? – Marius Hosting A very detailed walkthru on setting up a Reverse Proxy to go into a Docker Compartment. Exactly what I was looking for. Just tested in with all the apps, and it appears to work great. He has other walkthrus for the Plex ecosystem. I haven't looked, yet, to see what else he has.

Hopefully this will save someone else a lot of searching.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.