Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: skylist.aero
I ran this command: Install
It produced this output: Lets Encrypt certificate
This certificate will no longer be used for skylist.aero
Error: Could not issue a Let’s Encrypt SSL/TLS certificate for SKYLIST.AERO.
Details
Install certificate failure: Unable to set certificate name :
My web server is (include version):101domain (Plesk)
The operating system my web server runs on is (include version): Wordpress
My hosting provider, if applicable, is: 101domain (Plesk)
I can login to a root shell on my machine (yes or no, or I don’t know): I don’t know
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): Yes (plesk)
You should modify the TITLE to something more like: Plesk (101domains) install cert failure: Unable to set cert name
(It should attract more attention from the ones that can help the most)
If all else fails, try the Plesk Forum
ALSO: https://crt.sh/?q=skylist.aero
There are too many certs recently issued for that exact domain.
The error message may be inaccurate.
You could try renewing a new cert that contains the WWW; which would be seen as a different request and falls under a different set of rate limits.
Or include a name that you haven’t issued yet (like: mail.skylist.aero)
You can try
“skylist.aero + www.skylist.aero”
“skylist.aero + www.skylist.aero + mail.skylist.aero”
“skylist.aero + www.skylist.aero + mail.skylist.aero + webmail.skylist.aero”
NOTE: Adding new combinations won’t bypass rate limits altogether.
It just hits a different limit - I think that one is 20 certs per week per domain.
Until you figure out how to get it to work, you might also want to try using the LE STAGING/TEST system instead of the LE LIVE/PRODUCTION system.
I don’t know how that can be done using Plesk.
Otherwise, I suggest you read about rate limits and understand them before proceeding.
See: https://letsencrypt.org/docs/rate-limits/