SOLVED SaaS Application & Multidomain SSL

[ehask71]

I have an app that we built and for PCI compliance reasons we had on a plain jane linux server LAMP setup and used an A record's to point clients subdomains to it.

Well I spent the last week getting our CPanel Servers PCI compliant ..... ugh so know I want to do away with the Plain Cent 7 box.

It has a base domain lunch.*********.com and a static IP. Clients are instructed to add an A record pointing to the same IP address once we add the virthost and the subdomain to our Multi Domain SSL and it just works and has for the last six months.


<VirtualHost 74.50.**.***:443>
ServerName seffnerpay.******.org
DocumentRoot /home/lunch/public_html

<VirtualHost 74.50.**.***:443>
ServerName tampapay.******.org
DocumentRoot /home/lunch/public_html

<VirtualHost 74.50.**.***:443>
ServerName lunch.******.com
DocumentRoot /home/lunch/public_html


SSLCertificateFile /home/lunch/ssl/lunch_**********_com.crt
SSLCertificateKeyFile /home/lunch/ssl/lunch.**********.com.key
SSLCACertificateFile /home/lunch/ssl/lunch_***********_com.ca-bundle


Now on my CPanel I created the lunch subdomain with a static IP loaded the Key and Crt for the Multidomain SSL . Add the Virthosts for Seffner & Tampa in the post_virtualhost_2.conf

When I go to lunch.*******.com it works fine but tampa and seffner it throws

This server could not prove that it is tampapay.********.org; its security certificate is from lunch.********.com. This may be caused by a misconfiguration

the requests are coming in for tampa and seffner ....

Any ideas???

 

[ehask71]

Ok I just figured it out while looking over the SSL Hosts .......

For some reason when I installed the CERT, Key and Bundle before it didnt take and I noticed the Issuer was CPanel not Comodo. I deleted the SSL host, mv post_virtualhost_2.conf to post_virtualhost_2.conf.OLD (have to do this cause installing a SSL triggers httpd restart), reinstalled my MultiDomain SSL , adjusted the paths in post_virtualhost_2.conf.OLD, mv back to post_virtualhost_2.conf, and restarted httpd and boom its working fine

Im not deleting in case someone is doing similar.

Mods feel free to delete if you feel it should.

 

[Infopro]

Thanks for updating the thread with your findings on this issue.