This server could not prove that it is example.com error

GoWilkes

• September 10, 2018 19:16

I'm trying to update a website on my server to run all pages through SSL, but I'm getting the following error when I visit the page: This server could not prove that it is www.example.com; its security certificate is from anothersite.com. This may be caused by a misconfiguration or an attacker intercepting your connection. In this case, anothersite.com is the primary account on my server, but I don't know why or if I should change that; I just saw that for the first time under "Manage SSL Hosts". I'm guessing that it's the primary account because it's first alphabetically? Also under "Manage SSL Hosts" and "SSL Storage Manager", I see that example.com isn't listed. I have a subdomain for it that's listed under both (new.example.com), but not the main domain itself. But the account IS listed under "Manage AutoSSL", and is set to "Enable AutoSSL". I can generate a certificate, but then it's self-signed instead of issued by cPanel, and I'm not sure that this is quite the same. So what do I do to make WHM generate a certificate for this account?

• 

  GoWilkes

  • September 11, 2018 01:43

  Update... it looks like I have 3 domains that aren't installing the certificate, and I don't know why. In the AutoSSL log I have the same error for all three of them: Checking websites for "example" " 3:38:05 AM Analyzing "example.com" " 3:38:05 AM ERROR TLS Status: Defective ERROR Defect: NO_SSL: No SSL certificate is installed. All 3 show up under "Pending Queue" as of Sept 7, but that's 3 days ago... I also notice that all 3 of them have had a paid certificate in the past (but not now), and all 3 are listed under the same reseller's account instead of "root". Buuuut, there are other accounts under that reseller that have no problem, so I don't know if that's really related to the problem.

  0
• 

  GoWilkes

  • September 11, 2018 07:04

  The server provider sent a ticket to cPanel, and they were able to fix it... the problem was that the .htaccess had blocked a bunch of IPs, and that was preventing the DCV check from passing. They removed the .htaccess, let it pass, then re-enabled the .htaccess.

  0
• 

  cPanelMichael

  • September 12, 2018 18:16

  The server provider sent a ticket to cPanel, and they were able to fix it... the problem was that the .htaccess had blocked a bunch of IPs, and that was preventing the DCV check from passing. They removed the .htaccess, let it pass, then re-enabled the .htaccess.

  
  Hello, I'm glad to see the issue was solved. Thank you for reporting the outcome.

  0

Please sign in to leave a comment.