Unable to validate domainname

Help
1

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. crt.sh | 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: nieuwmail.nl

I ran this command: renew

It produced this output: Unable to validate

My web server is (include version): Synology DSM 7.1.1-42962 Update 7

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

My hosting provider, if applicable, is: Vimexx

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

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

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): Don't know what that is.

For years I was able to automatically update the certificate, but now it fails. Also when I turned off my "firewall" and "Automatically blocking".

I did run the online tool https://letsdebug.net and it shows:
All OK!
OK
No issues were found with nieuwmail.nl. If you are having problems with creating an SSL certificate, please visit the Let's Encrypt Community forums and post a question there.

Please help!

2

Does it provide a more detailled log? Because without any details and a successful Let's Debug it's very hard to figure out what the issue is.

That said, I do see there's something not entirely functioning with one of the nameservers of your domain, ns4.dns.nl: its IPv6 address 2620:10a:80ac::200 seems to be malfunctioning for some parts of the internet.

E.g., I cannot reach its DNS server, nor can Dig web interface - online dns lookup tool. But if you look at https://dnsviz.net/d/nieuwmail.nl/Z27w3g/responses/, they don't have an issue, nor does UnboundTest at https://unboundtest.com/m/A/nieuwmail.nl/CYY4KWOP (although the latter doesn't seem to have queried 2620:10a:80ac::200 specifically.)

Not sure if the above has anything to do with the failure, but that's the only thing I could find.

2 Likes
3

Most likely this is just supplemental information

Here are community forums for Synology that may be of assistance as well:

  1. https://community.synology.com/enu
  2. https://www.synoforum.com/
  3. https://synocommunity.com/

kb.synology.com

I see a "Not Secure" warning when connecting to my Synology device via HTTPS....

Synology Knowledge Center offers comprehensive support, providing answers to frequently asked questions, troubleshooting steps, software tutorials, and all the technical documentation you may need.

2 Likes
4

Hello everyone thanks,
I have no idea what happened, I didn't find anything I could change.
However, after a few days it suddenly works to validate.
Thanks, Renee

2 Likes
5

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