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.
I ran this command: I want to issue a cert for this subdomain but the system says an expired cert already exists. yet we did not create it and my Client states that the cert was not created by them either. Please let me know if you can cancel that expired cert.
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or 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):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
Thanks for your reply @griffin but how do I get rid of that old cert? I don’t want any error message to show up. I did not even create that cert to begin with.
I want to have the page completely unsecure and not give users a cert security error message when the page loads.
If it's your server, you'll need to configure it to serve whatever cert you want or to remove the cert. If you post your nginx or Apache or whatever configuration, somebody here may be able to help you.
If this is a "shared hosting" type of plan, where you don't have direct access to the server, then you probably need to use whatever control panel they've provided or contact your hosting company.
Let's Encrypt provides certificates, but it's up to you to configure and use them (though there are a lot of tools out there to help automate it). People here may be able to help you, but you left a lot of the initial questionnaire blank which makes it more difficult to help you. But if you don't know your web server software, control panel software, or hosting provider, then people here probably don't either.
@QuezMedia
As there are certs from multiple domain on that server, I presume that it is in some way a "shared system".
Please notify the admin of that system about this problem:
The nginx configuration is clearly using the wrong cert for your domain.
