• 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 Install the certificate let's encrypt

elena

New Pleskian
I try to install the certificate let's encrypt in one of my domains, but this error appears:

I updated to 2.0.1

Error: Error de instalación del certificado SSL Let's Encrypt: Challenge marked as invalid. Details: Invalid response fromhttp://dominio.com/.well-kn... "<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>403 Forbidden</title>
</head><body>
<h1>Forbidden</h1>
<p"
 
Thanks, I know the way of installation.
I have several domains in the same Plesk panel, all configured in the same way and only gives me error in 2 of them.
 
Hi elena,

a "403 forbidden" error indicates, that you either denied the access for folders starting with a dot, or you use additional ".htaccess" and/or additinal nginx directives, which could prevent that the certificate challenge work as expected. In some cases, the additional nginx directive ( over => HOME > Subscription > YOUR-DOMAIN.COM > Apache & nginx Settings )
Code:
location ~ /.well-known {
  allow all;
}
... could solve your issue.

If this doesn't solve your issue, pls. consider to post corresponding configuration files from "/var/www/vhosts/system/YOUR-DOMAIN.COM/conf" and latest log - files from "/var/www/vhosts/system/YOUR-DOMAIN.COM/logs" for further investigations and IF you use as well ".htaccess" - files, pls. don't forget to include them as well.
 
Back
Top