SNI Serves Wrong SSL
I have a website (example.co.uk) which includes an addon domain (example.com). I've added an SSL for each domain but when I load and generates a browser error. What do I need to do to fix this error? I've checked the Apache configuration and it appears that it is pointing to the correct SSL:
SSLCertificateFile /var/cpanel/ssl/installed/certs/example_co_uk_9a1aa_$
Any help or pointers would be greatly appreciated!
-
Hello :) Have you verified your server supports SNI (e.g. CentOS/RHEL/CloudLinux 6.x or newer)? Thank you. 0 -
Hi BatGranny, What do you see under Home " SSL/TLS " Manage SSL Hosts in WHM? Is the shared button already enabled for example.com or is it disabled? 0 -
Thanks for the replies. The OS and WHM version are CENTOS 6.6 x86_64 and WHM 11.50.0 (build 10) so SNI is supported. Hi BatGranny, What do you see under Home " SSL/TLS " Manage SSL Hosts in WHM? Is the shared button already enabled for example.com or is it disabled?
The button is there so there is an option to share example.com (also .co.uk if I select it in the dropdown), should I enable it?0 -
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. 0 -
Thanks for the replies. The OS and WHM version are CENTOS 6.6 x86_64 and WHM 11.50.0 (build 10) so SNI is supported. The button is there so there is an option to share example.com (also .co.uk if I select it in the dropdown), should I enable it?
It is fine as is. Just wanted to see it if it got enabled before and in what way. The only difference I can see is our WHM running build 29 while you are on 10. I doubt that would matter and will see if I can replicate your issue on build 29.0 -
Oddly, I transferred the account to a WHM dev box which is running WHM 11.48.4 (build 4) and it worked fine so I suspect the problem is either a configuration issue or a problem with WHM itself. 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.
I've opened ticket number 69597770 -
This is now sorted. It turns out that the client was running a CDN which he neglected to mention until this morning, and the CDN only had the example.com SSL applied to it. 0 -
I'm that you go it sorted out. Have a good one. :) 0 -
I'm happy to see the issue is now resolved. Thank you for updating us with the outcome. 0
Please sign in to leave a comment.
Comments
9 comments