install certificate on synology lets encrypt

What might be worth investigating is, if replacing the runtime environment that servs the DSM UI: I guess nginx could be replaced with a static compiled version, but what about synocgid - on of both must be responsible to execute the package manager's certificate cheks. Is it safe to replace the system libraries with those of the packages? I highly doubt that.

Select Replace the certificate and continue. Perform the following actions in the control panel. Once updated, your NAS is ready for the installation of the Let’s Encrypt SSL certificate. Without having identified what exact dependcy an affected application requires, it is hard to figure out what needs to be replaced.Īll 3rd party spk packages should come with updated version of openssl - but those are private to the package. To install this update, go to the Update tab in your NAS control panel and select DMS update. You can prebuild static compiled curl binaries from github right away and test it. I've tried it in 3 browsers (Brave, Safari & Edge) they all report the same.I doubt that replacing curl with a static compiled version will solve much issues, other than maybee with custom scripts that depend on curl.

I've cleared the cache on the browser, no change. Which looks good, but if I access the NAS via I still get a not secure error and the certificate still shows as. Wow that worked! So I now have three certificates installed: Please make sure the domain name is valid.' again. It still fails with the error message of 'Failed to connect to Let's Encrypt. But this certificate will only be used by. I'll leave the DNS settings as they are for the moment. If you use DSM 6.1 on a Synology NAS, then requesting an SSL certificate from Lets Encrypt is very easy. Since realizing that, I have been using names in the domain name field of LE and it has been flawless. Turns out I was using under domain name, but that was wrong since it technically points to a hosted google site (technically the verification is that google has possession of this domain name and uses their own cert for the root domain). In my case when I first started (and thanks to for all his support), I was getting the same error. Anytime I need to create an additional domain name related to the synology, I just use a new in the domain name portion of LE and works without issue. I am then able to create a LE cert Domain =, my email address, and if you want add in SAN names, including. I then created a subdomain (CNAME) called which points to. On my domain account this is setup as an A record. I then used google DDNS in synology, address is. lands on a website hosted by google websites. In my setup is hosted by google domains. Use a subdomain to register the LE certs. I'm not exactly sure what you're looking to do, but here is my experience with that error.

Install certificate on synology lets encrypt