Web Hosting Talk : Web Hosting Main Forums : Hosting Security and Technology : SSL and subdomains

[webink]

Ok I have googled high and low and i'm about to explode. This has been an issue for the last 4 days...

I have secure.domain.com

I bought a SSL cert for secure.domain.com

I installed the cert

http://secure.domain.com shows the right content

https://secure.domain.com shows the content for http://www.domain.com

-
I've had this working before on site5, but I share a dedicated account now with WHM/cPanel and it's not working.

it's like the subdomain is being ignored.

-
Tll me if i'm wrong, but each SSL needs its own IP correct? i added an IP for domain.com and WHM seems to have set it for all the subdomains as well.

I'm so lost Please help me!

[BF-Gary]

Yes you need to have a dedicated IP for SSL.

Can you use the real domain instead? Troubleshooting with fake domains makes it hard.

[webink]

What do you mean fake domain?

I just want to cry right now. How did site5 get it to work? When we had it setup before we moved servers it worked great. We had the main WWW subdomain and the SECURE subdomain.

Now I have created the SECURE subdomain on this server and it works fine as http://secure.domain.com but not as https://secure.subdomain.com

It's like the HTTPS is forcing all subdomains to point to the root domain :/


How do I get the SECURE subdomain to show its own content?

[BF-Gary]

Well this is a fake domain secure.subdomain.com.

[Timeprism]

This seems to be a webserver configuration problem. Set up a virtual host for secure.domain.com for HTTPS.

[webink]

Originally Posted by Timeprism

This seems to be a webserver configuration problem. Set up a virtual host for secure.domain.com for HTTPS.

That's what I ended up doing. WHM didnt setup the IPs correctly for the vHost. So I had to go in and hand edit the httpd.conf

Good experience though, taught me a few things.

Now to grow my hair back.