# Let's Encrypt on Synology + web station : https fail

**URL:** <https://community.letsencrypt.org/t/lets-encrypt-on-synology-web-station-https-fail/140349>\
**Category:** Help\
**Created:** [December 11, 2020, 3:08pm UTC](https://community.letsencrypt.org/t/lets-encrypt-on-synology-web-station-https-fail/140349 "2020-12-11T15:08:02Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ThomasN](https://avatars.discourse-cdn.com/v4/letter/t/b782af/32.png) [@ThomasN](https://community.letsencrypt.org/u/ThomasN)\
**Post date:** [December 11, 2020, 3:08pm UTC](https://community.letsencrypt.org/t/lets-encrypt-on-synology-web-station-https-fail/140349/1 "2020-12-11T15:08:02Z")

</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: [http://www.thomasnaude-photographie.fr/](http://www.thomasnaude-photographie.fr/)

I ran this command:  
creating of a certificate for a website hosted on a Synology NAS:  
nom de domaine: [www.thomasnaude-photographie.fr](http://www.thomasnaude-photographie.fr)  
courrier electronique: [thomas.naude@free.fr](mailto:thomas.naude@free.fr)  
Autre nom de l'objet: [www.thomasnaude-photographie.fr](http://www.thomasnaude-photographie.fr)

It produced this output: connexion not secure on the brother

My web server is (include version): Synology Web Station

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

My hosting provider, if applicable, is: Obambu

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

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

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

Thank you for your helper

---

<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:** [December 11, 2020, 4:26pm UTC](https://community.letsencrypt.org/t/lets-encrypt-on-synology-web-station-https-fail/140349/2 "2020-12-11T16:26:28Z")

</div>

Hi @ThomasN

> [@ThomasN](#):
>
> My domain is: [http://www.thomasnaude-photographie.fr/](http://www.thomasnaude-photographie.fr/)

that website has tons of wrong links.

```nohighlight
<link rel="canonical" href="https://192.168.0.110/tnphotographie/" />

```

- 192.168.\* is a private ip address, not public visible, so it's impossible that a user connects that ip
- You have a certificate with your domain name, not with the ip address. So https is always insecure

Your domain name is required.

And there are tons of a elements with the same problem.

---

<div class="post-metadata">

**Author:** ![ThomasN](https://avatars.discourse-cdn.com/v4/letter/t/b782af/32.png) [@ThomasN](https://community.letsencrypt.org/u/ThomasN)\
**Post date:** [December 12, 2020, 8:29am UTC](https://community.letsencrypt.org/t/lets-encrypt-on-synology-web-station-https-fail/140349/3 "2020-12-12T08:29:37Z")

</div>

> [@JuergenAuer](#):
>
> `https://192.168`

Hello 🙂  
Okay ! I had not seen these links http: [//192.168](https://192.168) ..  
I think the problem comes from this:  
This is a site that I migrated from my host to my Synology NAS. And access to [http://www.thomasnaude-photographie.fr/wp-admin](http://www.thomasnaude-photographie.fr/wp-admin) does not work, only [https://192.168.0.110/tnphotographie/wp-admin](https://192.168.0.110/tnphotographie/wp-admin) works! so on restore (updraft plus) i think it turned all links to https: [//192.168.0.110/tnphotographi](https://192.168.0.110/tnphotographi) ... weird .. domain name problem?

---

<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:** [December 12, 2020, 9:53am UTC](https://community.letsencrypt.org/t/lets-encrypt-on-synology-web-station-https-fail/140349/4 "2020-12-12T09:53:24Z")

</div>

> [@ThomasN](#):
>
> domain name problem?

I don't know why you have that problem.

In WordPress, it would be the wrong basic url.

But you have to change that. These urls can't work with your certificate.

---

<div class="post-metadata">

**Author:** ![ThomasN](https://avatars.discourse-cdn.com/v4/letter/t/b782af/32.png) [@ThomasN](https://community.letsencrypt.org/u/ThomasN)\
**Post date:** [December 12, 2020, 12:37pm UTC](https://community.letsencrypt.org/t/lets-encrypt-on-synology-web-station-https-fail/140349/5 "2020-12-12T12:37:36Z")

</div>

Ok I will solve this problem. Thanks a lot for your help !!

---

<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:** [January 11, 2021, 12:37pm UTC](https://community.letsencrypt.org/t/lets-encrypt-on-synology-web-station-https-fail/140349/6 "2021-01-11T12:37:41Z")

</div>

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