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.
My domain is: houseofprayer[.]org
I ran this command: Renewed existing Cert
It produced this output: A valid SSL Cert, then a few hours later SSL Cert changed (see image)
I just checked again in Chrome and the Original Cert is back. What would be causing this? As you can see the common name on the cert changed from houseofprayer[.]org topxy.prd.live.c2szps.spcld[.]net. This happened within a few hours of renewing the cert both yesterday and today.
To @rg305, I have not had a problem with any other sites. I did receive the bad cert on 2 different machines in 2 different locations, although I was using the same Chrome account on both machines. I do have another test website running the same Bitnami LAMP stack on MS Azure with a Lets Encrypt Cert and have not had any problems with that site. hoptest.org
OK, here we go again. I just tried to access site with MS Edge and now getting security errors.
I also tried using a second Chrome account, Desktop and Mobile, same security error.
If I assume this server is compromised, can I just move site to another server or will I still get the same errors? Is the security cert tied to the domain/common name or the physical server itself?
OK. I did find some malware on my PC, which I removed. The site appears to be working again. Since both of the 3rd party sites showed passing scores I will just assume the site is secure. Now that I think about it, I recently purchased a Cisco Meraki router and firewall and last week I finally activated the firewall features. Is it possible the firewall could be intercepting the website traffic and showing it as un secured? Although that does not explain my other work location showing security issues.
I was just trying to help isolate where this problem occurred. Just because it involved a faulty cert does not mean it is server related.
Often people think they are trying different things when they are not ... forgetting their devices may use the same antivirus or network firewalls and similar.
When I first looked at this problem right after you said it was failing I did not see anything wrong. Not from my own test servers or from those 3rd party sites. Which made me start thinking it was something unique to the devices you use and not the general public.
@stewe mentioned earlier about Barracuda / Comcast. There are many google hits of people with wrong DNS results for their in certain cases. I never saw the failure to be able to check that but if it recurs that is something to look at.