# Cannot renew certificate on Synology

**URL:** <https://community.letsencrypt.org/t/cannot-renew-certificate-on-synology/116442>\
**Category:** Help\
**Created:** [March 15, 2020, 7:09pm UTC](https://community.letsencrypt.org/t/cannot-renew-certificate-on-synology/116442 "2020-03-15T19:09:30Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![rnollen](https://avatars.discourse-cdn.com/v4/letter/r/8edcca/32.png) [@rnollen](https://community.letsencrypt.org/u/rnollen)\
**Post date:** [March 15, 2020, 7:09pm UTC](https://community.letsencrypt.org/t/cannot-renew-certificate-on-synology/116442/1 "2020-03-15T19:09:30Z")

</div>

Hi All,

I am using a DS414. On my Synology I always use to have the Let’s Encrypt certificates. Now, for some particular reason the Let’s encrypt certificate renewal process is not working anymore. it stopped a few months ago. .

I have tried so many things to get it running again; but still without any luck. My port 80 and 443 are open on the router. I have disabled the Synology Firewall; played around with the TLS settings on the security/advanced tab.  
The strange thing is, if I create a Let’s Encrypt certificate on .synology.me it works; when I do the same with my own Domain name it doesn’t work (also when I use the Alternative name). But both names points to the same IP adress. It almost looks like something with the domain namespace itself is not working OK

The messages log shows me this (changed the domain name in the log):

_DiskStation kernel: [4922553.662408] init: upnpd main process (5036) killed by KILL signal_  
_DiskStation syno-letsencrypt: syno-letsencrypt.cpp:116 Failed to do new authorization, may retry with another type. [{“error”:202,“file”:“client\_v2.cpp”,“msg”:“Failed to setup challegne for .nl of http-01”}_  
_]_  
_DiskStation kernel: [4922573.602793] init: upnpd main process (5325) killed by KILL signal_  
_DiskStation syno-letsencrypt: syno-letsencrypt.cpp:116 Failed to do new authorization, may retry with another type. [{“error”:200,“file”:“client\_v2.cpp”,“msg”:“do new auth by path: failed to do challenge.”}_  
_]_  
_DiskStation synoscgi\_SYNO.Core.Certificate.LetsEncrypt\_1\_create[4892]: certificate.cpp:973 syno-letsencrypt failed. 102 [Failed to new certificate.]_  
_DiskStation synoscgi\_SYNO.Core.Certificate.LetsEncrypt\_1\_create[4892]: certificate.cpp:1392 Failed to create Let’sEncrypt certificate. [102][Failed to new certificate.]_

Anyone got an idea where to look or how to fix this? Tried so many things that where suggested on sites but don’t know where to look next or how to fix this error… 🙂

Thanks!

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [March 15, 2020, 7:13pm UTC](https://community.letsencrypt.org/t/cannot-renew-certificate-on-synology/116442/2 "2020-03-15T19:13:36Z")

</div>

Hi @rnollen

> [@rnollen](#):
>
> The strange thing is, if I create a Let’s Encrypt certificate on .synology.me it works; when I do the same with my own Domain name it doesn’t work (also when I use the Alternative name).

your domain names are required.

---

<div class="post-metadata">

**Author:** ![rnollen](https://avatars.discourse-cdn.com/v4/letter/r/8edcca/32.png) [@rnollen](https://community.letsencrypt.org/u/rnollen)\
**Post date:** [March 15, 2020, 7:31pm UTC](https://community.letsencrypt.org/t/cannot-renew-certificate-on-synology/116442/3 "2020-03-15T19:31:47Z")

</div>

My domain name is [rnollen.synology.me](http://rnollen.synology.me) and www.rnollen.nl; I want to create a certificate on the second one…🙂

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [March 15, 2020, 7:44pm UTC](https://community.letsencrypt.org/t/cannot-renew-certificate-on-synology/116442/4 "2020-03-15T19:44:58Z")

</div>

> [@rnollen](#):
>
> Failed to do new authorization, may retry with another type. [{“error”:202,“file”:“client\_v2.cpp”,“msg”:“Failed to setup challegne for .nl of http-01”}

Looks like you need to "register" your domain, so Synology knows you use that domain. You don't want to create a certificate with 'nl', looks like a general error of your configuration.

I'm not firm with Synology, perhaps ask in a Synology forum.

There is a blog, not the typical Synology login.

Checking your domain - [https://check-your-website.server-daten.de/?q=rnollen.nl](https://check-your-website.server-daten.de/?q=rnollen.nl) - the `rnollen.nl` doesn't have an ip address. May be a problem, may be not.

---

<div class="post-metadata">

**Author:** ![rnollen](https://avatars.discourse-cdn.com/v4/letter/r/8edcca/32.png) [@rnollen](https://community.letsencrypt.org/u/rnollen)\
**Post date:** [March 15, 2020, 8:01pm UTC](https://community.letsencrypt.org/t/cannot-renew-certificate-on-synology/116442/5 "2020-03-15T20:01:49Z")

</div>

Unfortunately on the Synology forum they don’t know the answer; and I was redirected here.  
I think the reason you don’t see an ip adress then. In the pas I always used a cname pointing to my A host record. Changed that because of these issue’s (also I don’t think I ever had a different IP yet)…

To register the domain on my synology; the problem is that I don’t know exactly what to do on the Synology for this? I don’t see anything written about this. ☹

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [March 15, 2020, 9:49pm UTC](https://community.letsencrypt.org/t/cannot-renew-certificate-on-synology/116442/6 "2020-03-15T21:49:18Z")

</div>

> [@rnollen](#):
>
> the problem is that I don’t know exactly what to do on the Synology for this?

I don't know if Synology supports that what you want.

Independend domain name -\> same ip address -\> Synology is able (or not able) to create a certificate.

---

<div class="post-metadata">

**Author:** ![rnollen](https://avatars.discourse-cdn.com/v4/letter/r/8edcca/32.png) [@rnollen](https://community.letsencrypt.org/u/rnollen)\
**Post date:** [March 16, 2020, 12:38pm UTC](https://community.letsencrypt.org/t/cannot-renew-certificate-on-synology/116442/7 "2020-03-16T12:38:00Z")

</div>

No; basically I want to use my own domain name only… the problem is that the DDNS domain name seems to work, but not my own domain name. It is not supported to have different domain names in the alternate name of the Synology.

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [March 16, 2020, 12:55pm UTC](https://community.letsencrypt.org/t/cannot-renew-certificate-on-synology/116442/8 "2020-03-16T12:55:30Z")

</div>

have you tried following these instructions? [Certificate | DSM - Synology Knowledge Center](https://www.synology.com/en-global/knowledgebase/DSM/help/DSM/AdminCenter/connection_certificate)

you can have one or both domains, one goes in Common Name, and ALL go in Subject Alternative Name.

* * *

is `83.82.46.203` your current ip address?

> [@rnollen](#):
>
> the DDNS domain name seems to work

it doesn't, I see a selfsigned cert.

---

<div class="post-metadata">

**Author:** ![rnollen](https://avatars.discourse-cdn.com/v4/letter/r/8edcca/32.png) [@rnollen](https://community.letsencrypt.org/u/rnollen)\
**Post date:** [March 16, 2020, 3:38pm UTC](https://community.letsencrypt.org/t/cannot-renew-certificate-on-synology/116442/9 "2020-03-16T15:38:08Z")

</div>

That certificate is currently attached to the site (for now) 🙂 IP adress is correct. I have tried to create a certificate only for my domain name, but the problem is that this one fails… Don’t know why; it works when I create one only with the [rnollen.synology.me](http://rnollen.synology.me) name…don’t know what the difference could be. But this is as a test, in the end I only want to have my domain name assigned to the certificate ☹

---

<div class="post-metadata">

**Author:** ![rnollen](https://avatars.discourse-cdn.com/v4/letter/r/8edcca/32.png) [@rnollen](https://community.letsencrypt.org/u/rnollen)\
**Post date:** [March 23, 2020, 8:54pm UTC](https://community.letsencrypt.org/t/cannot-renew-certificate-on-synology/116442/10 "2020-03-23T20:54:29Z")

</div>

Anyone? Or must I create a ticket at Synology support? Thanks!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [April 22, 2020, 8:54pm UTC](https://community.letsencrypt.org/t/cannot-renew-certificate-on-synology/116442/11 "2020-04-22T20:54:39Z")

</div>

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