• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Issue Renewing Let's Encrypt Certificates on Wordpress-Sites not possible

Stelios

New Pleskian
Hello Community,

we have some problems with renewing Let's Encrypt Certificates on our Windows Server 2016 with Plesk 17.8.11 Update #15. The static websites renew the SSL-Certificates without problems. But we have a lot of customers with wordpress installed. The renewing process fails at this websites with these error messages (I read all KB-Articles to solve the problem, nothing helps):

Error: Could not issue a Let's Encrypt SSL/TLS certificate for domain.de.

The authorization token is not available at http://domain.de/.well-known/acme-challenge/jj-C8pSEDmevA3NwPBDyp7l4gsEqalnMrTkz8iTzk7w.
To resolve the issue, make it possible to download the token file from the URL above.
See the related Knowledge Base article for details.
Details
Invalid response from https://acme-v01.api.letsencrypt.org/acme/authz/sqlxLNNf_RSalreIz_-e7pEgZ8L9rfjFZYiehsYFAEI.
Details:
Type: urn:acme:error:unauthorized
Status: 403
Detail: Invalid response from http://domain.de/.well-known/acme-challenge/jj-C8pSEDmevA3NwPBDyp7l4gsEqalnMrTkz8iTzk7w: "<!DOCTYPE html>
<html lang="de-DE">
<head>
<meta charset="UTF-8">
<link rel="profile" href="XFN 1.1 profile">
<link re"
 
Again the same error message. I think the problem is related to wordpress-websites as static sites work fine.
I also tried disabling the URL-Rewrite (and other suggested solutions) but this doesn't work also.
 
Hi @Stelios.

Seems like IIS forbids access to the specified URL by some reason. The typical reasons are file permissions, url rewrites, http auth (it could be turned on by "Password protection" option in WordPress Toolkit UI, so, please check this).

1. What do you see when you open the URL via your web browser?
2. Could you check the webserver logs, maybe IIS reported the reason why it forbids the access?
3. Also, try to find files with name "web.config", and if such files present, examine their content for DDL inclusion, rewrite rules and so on (if you have no idea how to examine such files you can send them to me in private message).
 
Hello Ruslan,

there is no active password protection in Wordpress-Toolkit.

1. Error 404. The page not found.
2. The Logs only show the 404 error.
3. As I wrote before I tried all suggested fixes in the KB-Articles. I also deleted the web.config files and disabled all rewrite rules. The error still remains.

The strange thing is that some Wordpress websites work and some do not. I have not found what the reason is...
 
Back
Top