• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Lets Encrypt Error - No valid ip adress

DuerrSteidle

Basic Pleskian
Hello,

I have a problem with renewing a certificate on my server. "example.com"

I have a sudomain (test.example.com )of ths domain where everything works.

The certificate has also been issued before, but it has now expired and I just wanted to renew it. Otherwise, I have not made any changes to it.

How can I find out what is causing this?

Thanks for your help

Greetings
 
Last edited:
Detail: No valid IP addresses found for webmutanten.org

Please check that the domain name can be resolved to the correct IP address against some of the global DNS resolvers:

# dig webmutanten.com @8.8.8.8 +short

If it is OK, check that at least one of the authoritative NS servers is not responding.

Let's encrypt checks all authoritative domain name server to make sure it resolves. Although having at least one working NS server is enough to keep the domain running if at least one of the authoritative DNS servers is not responding, the check will fail.

Identify the authoritative Name servers:

# whois webmutanten.com | grep Name

Make sure all name servers response:

# dig webmutanten.com @NS1.NAMESERVER.COM +short

Fix the server which is not responding.
 
Back
Top