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. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
It produced this output: Could not issue an SSL/TLS certificate for darbysys.com
Details
Could not issue a Let's Encrypt SSL/TLS certificate for darbysys.com. Authorization for the domain failed.
Please note that if a successful issuance the first time does NOT result in the proper USE of that certificate, re-issuing it again and again does not fix the latter problem, as it's not issuance related.
Depending on how you installed the certificate in the first place it might be as simpel as just reloading the webserver. Or perhaps the location of the certificate has changed and the webserver configuration needs to be changed. It all depends on what happened exactly at issuance.
Also note that your currrent certificate lacks the wildcard hostname, which your previous certificate did have. So it seems you did not renewed your previous certificate, but you issued a brand new certificate. Which might explain why your webserver doesn't pick it up.
OR... maybe it isn't using certbot
Hard to tell, since you didn't mention which ACME client is being used.
You did, however, mention Plesk - But I don't use Plesk, so I can't be certain how it deals with certs.
