Issue Let's Encrypt trouble

[newbe]

Server operating system version

Windows Server 2012 R2

Plesk version and microupdate number

Version 18.0.47 Update #5

Hi guys,

I have been using Let's Encrypt for a while now. Everything worked just fine, even auto renew. Nowadays, after Plesk update, things isn't that smooth. For instance auto renew does no longer work. For the site mobile.ibrf.se the certificate has expired, and I'm not able to renew the certificate. I'll get different error messages each time.

1. So I create a new subdomain for test: m.ibrf.se, and added a Let's Encrypt certificate which resulted in the error message:
   
   Could not issue an SSL/TLS certificate for m.ibrf.se
   Details
   Could not issue a Let's Encrypt SSL/TLS certificate for m.ibrf.se.
   
   => However, when checking the certificate has been installed and working.
   
   
2. When trying to add certificate for mobile.ibrf.se, I'll get the following error message:
   
   Could not issue an SSL/TLS certificate for mobile.ibrf.se
   Details
   Could not issue a Let's Encrypt SSL/TLS certificate for mobile.ibrf.se. Authorization for the domain failed.
   
   Details
   Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/178709602037.
   
   Details:
   Type: urn:ietfarams:acme:error:connection
   
   Status: 400
   
   Detail: 207.180.229.151: Fetching https://acme-challenge.localhost/.w...e/KW19IXEhTvYcCfLMW5eADXOdJ9dlfF-DHJFJfqOOOrM: Invalid hostname in redirect target, must end in IANA registered TLD

I'm pretty confused. How can I trouble shoot what´s going on ?

PLESK Version:
Plesk Obsidian Web Pro Edition
Version 18.0.47 Update #5

 

[IgorG]

Third-party Helicon "ISAPI_Rewrite 3 - Apache .htaccess mod_rewrite compatible module for IIS"
Go to Domains > example.com > File Manager page and rename .htaccess file.
It should help.

 

[newbe]

Hello IgorG,

I'm sorry, but I have no such file(s).

 

[newbe]

... we'll it turns out the that certificate has been updated after all, even when I received errors each time running reissue. Isn't this strange?

Events:
1. Site can't be reached
2. Reason: Site certificate has expired, even if auto renew is selected
3. Trying to renew manually - getting different error messages each time. Last time a LIMIT error is issued
4. Moving the site to a new subdomain and apply Let's encrypt certificate without and issues
5. Two days later, checking the old site site/certificate again, now using the let's debug tool. The certificate now seems OK
6. Checking the site, yes, the certificate is now OK. Somehow this issue fixed it's self!? How can this be?

I'm not to impressed by PLESK. A previous trivial task, feels now more like rocket science, moreover a fragmented help/documentation doesn't help much.