# Unable to renew or create certificate via Synology NAS **URL:** \ **Category:** Help\ **Created:** [May 18, 2019, 6:19am UTC](https://community.letsencrypt.org/t/unable-to-renew-or-create-certificate-via-synology-nas/93894 "2019-05-18T06:19:14Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![jnrfalcon](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jnrfalcon/32/31929_2.png) [@jnrfalcon](https://community.letsencrypt.org/u/jnrfalcon)\ **Post date:** [May 18, 2019, 6:19am UTC](https://community.letsencrypt.org/t/unable-to-renew-or-create-certificate-via-synology-nas/93894/1 "2019-05-18T06:19:14Z")
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: jnrfalcon.studio I ran this command: syno-letsencrypt new-cert -d jnrfalcon.studio -m _myemail_@gmail.com -v It produced this output: DEBUG: Dns01 challenge: Teardown [{“code”:“badparam”,“errinfo”:“delete.go:27”}]. DEBUG: DNS challenge failed, reason: {“error”:102,“file”:“client.cpp”,“msg”:“no valid domain name”} DEBUG: Normal challenge failed, reason: {“error”:107,“file”:“client.cpp”,“msg”:“jnrfalcon.studio: Fetching [https://jnrfalcon.studio/.well-known/acme-challenge/{hiden}:](https://jnrfalcon.studio/.well-known/acme-challenge/%7Bhiden%7D:) Timeout during connect (likely firewall problem)”} DEBUG: failed to open port 80. DEBUG: close port 80. {“error”:101,“file”:“client.cpp”,“msg”:“failed to open port 80.”} I own this domain and just rechecked that it is still current. Port 80 and 443 are both open and directed to the NAS. So no reason that the domain is not valid or the the port is not open. I also run the same for synology subdomain, works fine. So my guess is there’s some problem with Let’s Encrypt’s service that is discriminating \*.studio. (Note: you’ll find the current cert is my synology subdomain because it automatically defaulted back to it when I deleted the unrenewable entry) Please fix. ---
**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:** [May 18, 2019, 7:53am UTC](https://community.letsencrypt.org/t/unable-to-renew-or-create-certificate-via-synology-nas/93894/2 "2019-05-18T07:53:43Z")
Hi @jnrfalcon > [@jnrfalcon](#): > > My domain is: jnrfalcon.studio there is a check of your domain, there is a critical problem visible - [https://check-your-website.server-daten.de/?q=jnrfalcon.studio](https://check-your-website.server-daten.de/?q=jnrfalcon.studio) There are ipv4- and ipv6-addresses: | Host | T | IP-Address | is auth. | ∑ Queries | ∑ Timeout | | --- | --- | --- | --- | --- | --- | | jnrfalcon.studio | A | 97.94.23.124 | yes | 1 | 0 | | | AAAA | 2600:6c54:7c00:2d2a:1691:82ff:fe6e:747e | yes | | | | www.jnrfalcon.studio | | Name Error | yes | 1 | 0 | But ipv6 doesn't answer, not port 80, not port 443: | Domainname | Http-Status | redirect | Sec. | G | | --- | --- | --- | --- | --- | | • [http://jnrfalcon.studio/](http://jnrfalcon.studio/) | | | | | | 97.94.23.124 | 301 | [https://jnrfalcon.studio/](https://jnrfalcon.studio/) | 1.056 | A | | | | | | | | • [http://jnrfalcon.studio/](http://jnrfalcon.studio/) | | | | | | 2600:6c54:7c00:2d2a:1691:82ff:fe6e:747e | -14 | | 10.030 | T | | Timeout - The operation has timed out | | | | | | | | | | | | • [https://jnrfalcon.studio/](https://jnrfalcon.studio/) | | | | | | 97.94.23.124 | 302 | [https://jnrfalcon.studio/en/](https://jnrfalcon.studio/en/) | 5.060 | N | | Certificate error: RemoteCertificateNameMismatch | | | | | | | | | | | | • [https://jnrfalcon.studio/](https://jnrfalcon.studio/) | | | | | | 2600:6c54:7c00:2d2a:1691:82ff:fe6e:747e | -14 | | 10.026 | T | | Timeout - The operation has timed out | | | | | | | | | | | | • [https://jnrfalcon.studio/en/](https://jnrfalcon.studio/en/) | -14 | | 10.026 | T | | Timeout - The operation has timed out | | | | | | | | | | | | • [http://jnrfalcon.studio/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](http://jnrfalcon.studio/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | | | | | | 97.94.23.124 | 301 | [https://jnrfalcon.studio/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](https://jnrfalcon.studio/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | 0.814 | A | | Visible Content: 301 Moved Permanently nginx | | | | | | | | | | | | • [http://jnrfalcon.studio/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](http://jnrfalcon.studio/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | | | | | | 2600:6c54:7c00:2d2a:1691:82ff:fe6e:747e | -14 | | 10.026 | T | | Timeout - The operation has timed out | | | | | | Visible Content: | | | | | | | | | | | | • [https://jnrfalcon.studio/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](https://jnrfalcon.studio/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | -14 | | 10.026 | T | | Timeout - The operation has timed out | | | | | | Visible Content: | | | | | That's a critical error because Letsencrypt prefers ipv6. So - remove your ipv6 address, create a certificate, then fix your ipv6 (or) - fix your ipv6 directly. You can use the online tool to check your ipv6 direct - [https://check-your-website.server-daten.de/?q=2600%3A6c54%3A7c00%3A2d2a%3A1691%3A82ff%3Afe6e%3A747e](https://check-your-website.server-daten.de/?q=2600%3a6c54%3a7c00%3a2d2a%3a1691%3a82ff%3afe6e%3a747e) PS: That's > [@jnrfalcon](#): > > So my guess is there’s some problem with Let’s Encrypt’s service that is discriminating \*.studio. wrong. studio is a top level domain, so you can create a certificate. ---
**Author:** ![jnrfalcon](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jnrfalcon/32/31929_2.png) [@jnrfalcon](https://community.letsencrypt.org/u/jnrfalcon)\ **Post date:** [May 18, 2019, 8:49am UTC](https://community.letsencrypt.org/t/unable-to-renew-or-create-certificate-via-synology-nas/93894/3 "2019-05-18T08:49:42Z")
Fixed by deleting AAAA record. Thanks! ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [June 17, 2019, 8:49am UTC](https://community.letsencrypt.org/t/unable-to-renew-or-create-certificate-via-synology-nas/93894/4 "2019-06-17T08:49:58Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.