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:
I ran this command:
I am using the synology control panel not command prompt
It produced this output:
The process has failed. Please login to DSM again.
My web server is (include version):
Synology DS1522+
The operating system my web server runs on is (include version):
DSM 7.2.2-72806 Update 9
My hosting provider, if applicable, is: Synology
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): No
Would you explain more about the error you are getting?
Because you have gotten 13 wildcard certs in the past 90 days. Some as recent as today.
Note that ports 80 and 443 are not used by Let's Encrypt when issuing a wildcard cert. Those are only used for an HTTP Challenge. A wildcard cert must use the dns-01 challenge which uses the public DNS system to validate your request.
Everytime I have tried to replace the certificate I get a pop up and all it says is "Process Failed. Please sign in to DSM and try again." When I check the current certificate within the control panel it still isn't the Let's Encrypt certificate. I guess it is sending the request properly but my server is not receiving the certificate once it is issued.
That might be something better asked at the Synology forum or support. As noted, you are getting many Let's Encrypt certs and your server is using them. The Synology people will know better why their panel is showing you those results.
Go to Control Panel -> Security -> Certificates, then click "Settings". In the "Configure" tab you'll be able to select which certificate is used for which service. I think you need to change "system default" for the DSM UI.
Note: I'm not using DSM in English, so the translated names may be slightly different for you.