CCSupport

Member
Dec 14, 2014
17
0
1
cPanel Access Level
Root Administrator
Hello all,

We are experiencing a very weird SSL issue and I wondered if anyone else has seen this. I will explain....

We recently migrated our main php website from one server to another. The original server was a Windows based one, the new server is Centos 6.6 - WHM/cPanel based. The migration went easy, however here's the path we took which might be related to the issue:

1) Copy site files from originating host
2) Create temp sub-domain (www2.) with a temp IP address
3) Setup the domain within cPanel
4) Point sub-domain to cPanel temp IP address
5) Get our wildcard domain SSL (Comodo Wildcard SSL) reissued from normal CSR within cPanel
6) Complete SSL installation within cPanel
7) Check that Cert was active within cPanel and WHM
8) Test site - Site test successful SSL (80/443)
9) Migrate orignating dedicated IP address to WHM
10) Change site IP address within WHM
11) Test site - Site fails SSL (443) - Fine on 80

Obviously no detail from the above list, however all pretty straight-forward apart from the IP migration. However that is now complete.

The issue....even though the SSL shows as installed within cPanel and WHM...when testing using a number of SSL Checkers it's showing as no SSL certs found.

I have removed the cert and reinstalled...still no good. The certificate as mentioned is a Wildcard, however it shows up correctly within cPanel and WHM.

For info just in case:

WHM - 11.46.1 (build 3)
PHP - 5.4.35

So, has anyone seen this issue before? It really is driving me crazy! :confused:

I am hoping I am just being really stupid! lol
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,913
2,202
363
Hello :)

Could you open a support ticket using the link in my signature so we can take a closer look? You can post the ticket number here so we can update this thread with the outcome.

Thank you.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,913
2,202
363
I noticed we advised you to use a different cipher to resolve the issue, but it was causing some issues with a particular PCI compliance scan. Feel free to update us with the outcome.

Thank you.