• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Error: Unable to obtain Let's Encrypt SSL certificate because of failed challenge for domain

Kingsley

Silver Pleskian
Hello;

I am having issues renewing SSL certificate for one of my client. below is the error.

Code:
Error: Unable to obtain Let's Encrypt SSL certificate because of failed challenge for domain "dearmama360.com":
Invalid response from http://dearmama360.com/.well-known/acme-challenge/bfTCz4Gk3mC7RSJZvIEahvPEYfj29G-qNpR7xyDPjdQ: "<!doctype html > <!--[if IE 8]> <html class="ie8" lang="en"> <![endif]--> <!--[if IE 9]> <html class="ie9" lang="en">

The domain is with www why is it looking for non www that does not exist?

Regards
 
allow http AND https, and with AND without www. letsencrypt write an encrypted key file in your httdocs, and acces it from lets encrypt servers to verify if your domain is the real applicant .
if the acces in http is forbiden, you will never can get a valid letsencrypt key...
when you will have received your key, you will can change you config http/https..www/no www
 
allow http AND https, and with AND without www. letsencrypt write an encrypted key file in your httdocs, and acces it from lets encrypt servers to verify if your domain is the real applicant .
if the acces in http is forbiden, you will never can get a valid letsencrypt key...
when you will have received your key, you will can change you config http/https..www/no www
Your answer is not clear, so you are saying the site url on plesk should be with www or non www?
 
I also got problem with ONE of 2 Domain Alias that is not getting a certificate.

Warning: Failed to resolve the challenge for <Domain_Alias> Details:
Failed to pass challenges for domain '<Domain_Alias>'

What can i do about it?
 
Hi Rar9,

What can i do about it?
To investigate the root cause of your issue, you should consider to post the relevant log - entries from your "panel.log" and using the "debug - log - level" - modus ( temporarily! ) might as well help, with more details at the logs.
 
Back
Top