How to identify which SSL certificate is being used on a site
PCs show ERR_CERT_REVOKED for a valid GoDaddy cert
What happened to the SSL Checker tool?
GoDaddy SSL Cert Problem - Firefox and Edge
Videos
Have dozens of PCs showing a revoked certificate error for a valid certificate. Machines not part of the domain are able to access the website without error.
the certificate thumbprints are identical.
The certificate was issued less than a week ago and definitely is not revoked.
GoDaddy's certificate verification page shows the cert is working
Affected PCs are able to contact and download the CRL
On a machine that shows the error in Chrome when you click the view the certificate it shows as valid.
Certificate hierarchy is the same back to the same root CA for PCs with and without the problem.
Some user profiles on the machine might work while other profiles have the error.
There were only a handful of google results for this problem (most 5-8 years ago).
Chrome is at the latest version on all the PCs used for testing.
Problem follows the PC in Edge and IE.
chrome://components/ on all machines sows the CRLSet is up to date
Seems like some sort of odd GPO setting I can't find.
yeah, it was retired. See below
https://community.spiceworks.com/product-plans
SSL Checker: As of June 16, 2020, Spiceworks is deprecating the SSL Checker tool. After this date, it will no longer be accessible for use.
So, it’s been a couple months since I used the SSL Checker tool on the Spiceworks IT Tools page but I went to use it today from a direct link that I had to that page but just I got directed back to the main tools page and SSL Checker is no longer an option.
Did this feature get pulled? It was a really great tool to use to cross-check what I had record of in our on-site Spiceworks installation for security certificate expiration dates with what was actively being pulled on the web.
I’m dealing with a GoDaddy SSL cert issue that GoDaddy is unable to solve themselves. I have an SSL cert I purchased from GoDaddy and because of how they handled another problem for me part of the certificate has been revoked and they can’t seem to understand this even though it’s easy to see and get verified by a 3rd party SSL checker.
The site won’t load in Firefox or Edge because of this problem. It does load in Chrome currently.
Here’s the part that is broken even after I’ve rekeyed the cert 3 times at GoDaddys request:
SSL Certificate is revoked
The certificate has been revoked. You should replace it with a new certificate as soon as possible.
OCSP Staple:
Not Enabled
OCSP Origin:
Revoked
CRL Status:
Revoked
One of the checkers that GoDaddy uses when I contact their support doesn’t show them this detail so they aren’t aware of it even though I’ve told multiple support people that this is the case.
How do I fix this?
Thanks!
Why not re-issue the cert? Create a new CSR, get a new cert, install the new cert. It should be free to do so.
Gregg
Just started using go daddy and having an issue with SSL
So my website is hosted on GitHub Pages but my domain is registered with GoDaddy and I bought an SSL certificate from GoDaddy as well.
I’m having trouble figuring out how to install the SSL because of the server type. I’m unsure what “server” my website is on. It’s just hosted on GitHub pages so I do not know the specifics of the web server and OS it’s running on.
So how do you know what server type to choose if this is the case? I keep seeing guides about going to the “Web hosting” category on the GoDaddy dashboard where you check what hosting package it is so you can see what web server you have. But I don’t have that so how do I choose the server type?
EDIT: Solution
For anyone using GitHub Pages, you do not need any service to verify the security of your account or have to get any SSL certificates from any site whether it’s purchased or free. So no GoDaddy, no cloud flare, none of that is needed. This is because GitHub already provides SSL for free when you tick the “Enforce HTTPS” box. Apparently whether you tick the box or not, you still have to wait for some time for it to actually take effect on your website.
It all of a sudden just started working for me as I’ve been scrolling the internet trying to find an answer. As I’ve seen with many other solutions I’ve googled searched, you just simply have to wait at least 24 hours (maybe not the exact amount but that may be it for your case) for enforce HTTPS option to take effect. Also make sure wherever you got your custom domain, make sure it’s configured to actually be used through HTTPS from whatever the service the custom domain is from so that the “enforce https” option from GitHub Pages can work.
Also, I agree with everyone saying that GoDaddy shouldn’t even be used. I will be transferring my domain in 60 days to get away from the service. You shouldn’t even use them even to just a buy a domain. They upsell to hell and back, directions for their products are horrible and I think it’s on purpose so that they force you to buy more of their shit.