wildcard certificate in shared ip

pnueda

• January 21, 2015 11:00

Hi, I've already tried the common guides but still not able to get my wildcard ssl cert working on a shared ip address. I have bought a wildcard ssl certificate for *.domain.com That certificate should work for /http://www.domain.com and shop.domain.com I installed it with the result of no errors and it seems to be working: see /https://domain.com/test/index.htm Then, when I try to go to the main website /https://www.domain.com/ but it loads broken The same url with standard http loads fine: /http://www.domain.com/ I checked tail -f /usr/local/apache/domlogs/shop.domain.com-ssl_log and it is logging an Err 500 message on every request. We need to enable ssl for both main website and online shop in the subdomain shop.domain.com I followed instructions in the following forum thread: I am running a Centos 6.6 server with cpanel 11.46 and apache 2.2.27 Strange detail: after installing ssl host in WHM, I shared it, however the column "Needs SNI?" is tagged as "No" for both main website and subdomain. Is not that supposed to be a "Yes" since the certificate was installed in a shared IP? What am I missing? Any help will be appreciated. Best regards, Paco

• 

  pnueda

  • January 21, 2015 16:30

  Update: I've found out why it is not working on main website. It is old outdated code using absolute paths i.e. http://... so it cannot load properly using https Problem persists on subdomain shop.domain.com It is an updated Prestashop, so it should work fine. However, when I try https://shop.domain.com/administrador/ the following error is recorded in shop.domain.com-ssl_log:
  62.175.212.10 - - [21/Jan/2015:18:20:26 +0100] "GET /administrador/ [COLOR="#FF0000">HTTP/1.1" 500 20 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.99 Safari/537.36"
  Note that it is trying to GET using HTTP and not HTTPS. Why would it be that?

  0
• 

  cPanelMichael

  • January 22, 2015 13:07

  Hello :) Do you have any rewrite rules or script configuration options that would use the non-secure URL? The best way to ensure the SSL certificate is working is to upload a simple test HTML page and attempt to load it with the secure URL. Thank you.

  0

Please sign in to leave a comment.