Let's Encrypt Certificate on Synology DS - Problem with renewal


#1

In October I installed wordpress on a Synology Diskstation.

For reaching it from the internet I requested a certificate from Let’s Encrypt which was not a problem, as it is a build-in feature.

After 60 days I received a mail from Let’s Encrypt Expiry Bot expiry@letsencrypt.org noting that the cert will end within a couple of days. I did renew the certificate on CLI by the command sudo syno-letsencrypt renew-all -vv after logging in to the Syno through ssh. Some minute later the expiry time was shown in the DS.

This can be verify on https://crt.sh/?Identity=06s01at14163.my-router.de. It even shows that all certificates have been issued by Let’s Encrypt.

Today, at 20:47 UTC+1:00 I received an email from Let’s Encrypt Expiry Bot expiry@letsencrypt.org saying that: "Hello,

Your certificate (or certificates) for the names listed below will expire in 0 days (on 21 Jan 17 18:47 +0000). Please make sure to renew your certificate before then, or visitors to your website will encounter errors.

06s01at14163.my-router.de"

From the time I received this mail the webserver can not be reached any more. Furthermore the time given in the mail would be reached 23 h after receiving the mail.

I am quite irritated. And would very much appreciate help in understanding this and solving the problem with the unreachable server.

Many thanks in advance.

r2b2


#2

On 23 Oct you obtained a cert for just that single domain (see https://crt.sh/?id=47868364 )

On 30 Oct you obtained a certificate for both 06s01at14163.my-router.de and 16-05-19-20-01.synology.me ( see https://crt.sh/?id=48822423 ). This is the certificate you have just renewed (https://crt.sh/?id=74500926 )

Since you have not renewed the one from the 23rd Oct ( as it’s not needed). You are receiving emails warning you it’s about to expire.

I can reach 06s01at14163.my-router.de from here - if you can’t reach it, it doesn’t appear related to the cert expiry.


#3

I can also reach this domain successfully.


#4

Yeah,

webside is back again.

Additionally there was an faulty PHP-code.

Many thanks to you.

TOPIC SOLVED


#5

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