• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved Let's Encrypt no error message, no errorlog

RaHa

Basic Pleskian
Version Plesk Onyx v17.5.3_build1705170317.16 os_Ubuntu 16.04
Let's Encrypt Version: 2.5.1-344

If i want to install a cert I get this message:

Fehler: Für checkip.net konnte kein SSL/TLS-Zertifikat von Let's Encrypt ausgestellt werden. Fehler bei der Autorisierung der Domain.

Zusätzliche Fehlerinformationen:
%%message%%

I cann't find an errorlog for more information.
Access to .well-known/acme-challenge/ is possible, domain has A- and AAAA-records.

Where is the errorlog of Let's Encrypt?
How can I resolve the problem?

Thanks for help!
 
The error you are describing is most likely caused by a wrong order in the configuraton process. You will probably FIRST have set the "Forward to SSL" before you have installed the certificate. In that case the certificate cannot be verified, because the request of the token will be redirected to the SSL version of the site, but the SSL version does not yet work, because the certificate is not yet present.

Solution: Go into "hosting settings" of the domain and remove the checkmark from the "Dauerhafte, für SEO geeignete 301-Weiterleitung von HTTP zu HTTPS" checkbox. Save the setting. Then try to obtain the certificate again.
 
Thanks all for help. Missing an error.log I cann't defined the error. The provider inform me: For the domain, the server's IPv6 address is not supplied. This leads to the problems you described with Let's Encrypt. I found that the nameserver didn't deliver AAAA. I reinstall DNS Self at the domain-provider and now it works.
 
Back
Top