User name: D3nnis3n
TITLE
Let's Encrypt wildcard cartificates cannot be renewed automatically
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Plesk Obsidian 18.0.28 Update Nr. 3, Ubuntu 18.04.4 LTS, AMD64
PROBLEM DESCRIPTION
When activating the auto-renewal of Let's Encrypt Wildcard Certificates (which should be possible as of Let's Encrypt Extension Version 2.7.0) the renewal is failing and the administrators gets sent the following message for all wildcard domains via e-mail:
Both [FIXED BUG] Unable to install a Let's Encrypt certificate: Order's status ("pending") is not acceptable for finalization or No order for ID and Unable to install a Let´s Encrypt certificate in Plesk: urn:ietf:params:acme:error:malformed are NOT applicable / do NOT fix the issue.
We are using Plesk as Primary DNS controller, so it's not either the known issue when using a third-party DNS server.
Let's Encrypt is configured to renew 90 days before expiring, with the cronjobs for renewal of both SSLit! and Let's Encrypt set to be executed every 1st Month instead of every day.
This issue does not happen for non-wildcard certificates, they renew fine. The issue did not happen on Plesk Onyx either, wildcards renewed fine back then.
STEPS TO REPRODUCE
1. Set renew-before-expiration = 90 in [ext-letsencrypt] in panel.ini.
2. Reconfigure the autorenew cronjobs to trigger every first of month.
3. Issue a autorenewing wildcard certificate for a domain.
4. Wait until it's renewal time.
5. See it hasn't been renewed and get the message:
Steps 1 and 2 are optional, it's not working with the default configuration either, unfortunately.
ACTUAL RESULT
The wildcard certificate is not automatically renewed and needs to be renewed manually.
EXPECTED RESULT
The wildcard certificate is automatically renewed.
ANY ADDITIONAL INFORMATION
See here: Issue - Let's Encrypt Issues with Renewal
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug / Help sorting out (Fixing it)
TITLE
Let's Encrypt wildcard cartificates cannot be renewed automatically
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Plesk Obsidian 18.0.28 Update Nr. 3, Ubuntu 18.04.4 LTS, AMD64
PROBLEM DESCRIPTION
When activating the auto-renewal of Let's Encrypt Wildcard Certificates (which should be possible as of Let's Encrypt Extension Version 2.7.0) the renewal is failing and the administrators gets sent the following message for all wildcard domains via e-mail:
* 'Lets Encrypt xxx' [days to expire: xx]
[-] *.xxx
[-] xxx
Invalid response from https://acme-v02.api.letsencrypt.org/acme/order/xxxxx/xxxxxx.
Details:
Type: urn:ietfarams:acme:error:malformed
Status: 404
Detail: No order for ID xxxx
Both [FIXED BUG] Unable to install a Let's Encrypt certificate: Order's status ("pending") is not acceptable for finalization or No order for ID and Unable to install a Let´s Encrypt certificate in Plesk: urn:ietf:params:acme:error:malformed are NOT applicable / do NOT fix the issue.
We are using Plesk as Primary DNS controller, so it's not either the known issue when using a third-party DNS server.
Let's Encrypt is configured to renew 90 days before expiring, with the cronjobs for renewal of both SSLit! and Let's Encrypt set to be executed every 1st Month instead of every day.
This issue does not happen for non-wildcard certificates, they renew fine. The issue did not happen on Plesk Onyx either, wildcards renewed fine back then.
STEPS TO REPRODUCE
1. Set renew-before-expiration = 90 in [ext-letsencrypt] in panel.ini.
2. Reconfigure the autorenew cronjobs to trigger every first of month.
3. Issue a autorenewing wildcard certificate for a domain.
4. Wait until it's renewal time.
5. See it hasn't been renewed and get the message:
* 'Lets Encrypt xxx' [days to expire: xx]
[-] *.xxx
[-] xxx
Invalid response from https://acme-v02.api.letsencrypt.org/acme/order/xxxxx/xxxxxx.
Details:
Type: urn:ietfarams:acme:error:malformed
Status: 404
Detail: No order for ID xxxx
Steps 1 and 2 are optional, it's not working with the default configuration either, unfortunately.
ACTUAL RESULT
The wildcard certificate is not automatically renewed and needs to be renewed manually.
EXPECTED RESULT
The wildcard certificate is automatically renewed.
ANY ADDITIONAL INFORMATION
See here: Issue - Let's Encrypt Issues with Renewal
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug / Help sorting out (Fixing it)
Last edited: