Facebook
Twitter- Server operating system version
- AlmaLinux 8.10 (Cerulean Leopard)
- Plesk version and microupdate number
- v18.0.72
On Plesk Obsidian v18.0.72 provided by Hosting Provider.
We are creating new subdomains for one domain via Rest API. Plesk automatically adds Let's Encrypt certificates after subdomain creation. This process takes in average 25 minutes, sometimes 45 minutes and in rare past cases 2 hours.
I have tried issuing the certificate after the subdomain has been created. I used REST API, on the CLI endpoint according to the Plesk Docs (How to issue a SSL/TLS certificate for a domain via REST API?) but it did not show any more effect other beeing logged in the action protocol and issuing the cert after 45 minutes.
I know that the Let's Encrypt Issue Speed can be related to many factors including DNS. However, I was wondering if there is a best practise in this case to issue new Let's Encrypt Certificates on newly created subdomain with minimal waiting time?
As I have seen there is also the possibility to issue certificates with the sslit extension. Would it be a better approach?
We are creating new subdomains for one domain via Rest API. Plesk automatically adds Let's Encrypt certificates after subdomain creation. This process takes in average 25 minutes, sometimes 45 minutes and in rare past cases 2 hours.
I have tried issuing the certificate after the subdomain has been created. I used REST API, on the CLI endpoint according to the Plesk Docs (How to issue a SSL/TLS certificate for a domain via REST API?) but it did not show any more effect other beeing logged in the action protocol and issuing the cert after 45 minutes.
I know that the Let's Encrypt Issue Speed can be related to many factors including DNS. However, I was wondering if there is a best practise in this case to issue new Let's Encrypt Certificates on newly created subdomain with minimal waiting time?
As I have seen there is also the possibility to issue certificates with the sslit extension. Would it be a better approach?
