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.
That depends on how you got the certificate in the first place, but unfortunately you're not giving us much information to work with.
There also seems to be have been issued a Sectigo EV certificate for that hostname: crt.sh | 14152169203. Why not use that one? You've probably payed big bucks for that cert.
If you are trying to get a cert on Windows Server the tool I work on https://certifytheweb.com is probably the easiest to use and manage.
With that you would:
download and install the app on the server, click New Certificate (and register a Let's Encrypt account),
then in your new managed certificate select the IIS site and let it populate the domains from IIS hostname bindings (recommended that you don't have blank hostnames in your bindings as that can lead to confusion later)
click Request Certficate to order a new cert and auto apply it to your site based on the matching hostnames in the IIS bindings. Renewal will then be automatic.
Periodically open the app every few months to check for important app updates
You may even already be using Certify Certificate Manager, if not you are most likely using either win-acme (command line) or Posh-ACME (powershell). If so let us know which one and we'll see how we can help.
As @Osiris has mentioned you are using a (quite recent) Sectigo certificate, and that was either manually applied or ordered via their enterprise ACME service (which you can also do with all the above tools). So you're not actually using Let's Encrypt currently as far as we can see.