# Synology "Replace Existing Certificate"

**URL:** <https://community.letsencrypt.org/t/synology-replace-existing-certificate/109893>\
**Category:** Help\
**Created:** [January 5, 2020, 1:03am UTC](https://community.letsencrypt.org/t/synology-replace-existing-certificate/109893 "2020-01-05T01:03:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![majorsl](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/majorsl/32/3845_2.png) [@majorsl](https://community.letsencrypt.org/u/majorsl)\
**Post date:** [January 5, 2020, 1:03am UTC](https://community.letsencrypt.org/t/synology-replace-existing-certificate/109893/1 "2020-01-05T01:03:35Z")

</div>

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. [https://crt.sh/?q=example.com](https://crt.sh/?q=example.com)), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: [themajorshome.com](http://themajorshome.com)

I ran this command: Synology GUI

It produced this output: Unable to connect to Let’s Encrypt, make sure the domain name is correct.

My web server is (include version): ngix

The operating system my web server runs on is (include version): Synology DSM6

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

I’m not too new to this, I setup my Synology a couple of years ago. It has been fine and renewing Let’s Encrypt ever since. Today, I wanted to replace the cert to add a couple more “Subject Alternative Names.” It is failing with the above error and I have no idea why. Nothing has changed and like I said, renewals have been chugging right along for years.

---

<div class="post-metadata">

**Author:** ![majorsl](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/majorsl/32/3845_2.png) [@majorsl](https://community.letsencrypt.org/u/majorsl)\
**Post date:** [January 5, 2020, 1:22am UTC](https://community.letsencrypt.org/t/synology-replace-existing-certificate/109893/2 "2020-01-05T01:22:33Z")

</div>

Ah, disregard. My bad. I also cleaned up and removed the wrong alternative name in my DNS. I assume LE was looking for it and not finding it.

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [January 5, 2020, 2:43am UTC](https://community.letsencrypt.org/t/synology-replace-existing-certificate/109893/3 "2020-01-05T02:43:45Z")

</div>

Make sure you keep your DSM software up-to-date and you should be fine 🙂

---

<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:** [February 4, 2020, 2:43am UTC](https://community.letsencrypt.org/t/synology-replace-existing-certificate/109893/4 "2020-02-04T02:43:49Z")

</div>

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