• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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