Page 1 of 1

SSL redirect to subdomain

PostPosted: August 29th, 2010, 12:08 pm
by Amphibian
Hey folks – my host has informed me that they can only install an SSL cert on a distinct IP from my main domain, so they had to use a subdomain *secure.my domain.com). Unfortunately, this means that the SSL redirect custom field in S2Member doesn't cut it, as it only changes 'http' to 'https' using the primary domain.

When I try to access the site directly using the 'secure.mydomain.com' address, WP simply kicks me back to the primary domain, I suppose sensing that the site was loaded using a different domain, perhaps for security reasons.

I guess what I'm looking for is two things:

1) a way to have s2Member do a secure redirect to the subdomain;
2) a way to keep WP from kicking me out of said subdomain.

Anyone know a way around this?

Thanks!

Re: SSL redirect to subdomain

PostPosted: August 30th, 2010, 12:58 pm
by Jason Caldwell
Hi there. Thanks for writing in.
my host has informed me that they can only install an SSL cert on a distinct IP from my main domain, so they had to use a subdomain *secure.my domain.com).

Sorry to hear that. Yea, that's not going to work well with WordPress®. It's a common issue that SSL certificates need to be attached to a dedicated IP address, but there are many ways for hosts to deal with this issue. One of the best approaches I've seen, is the new "Multiple Domains (UCC)" certificate sold by GoDaddy. This allows a site owner to purchase and install ONE certificate, that will work on the same IP, for multiple domains. NOT sub-domains, but different domains ( this type of certificate is brand new ).
http://www.godaddy.com/ssl/ssl-certific ... px?ci=8979
I guess what I'm looking for is two things:
1) a way to have s2Member do a secure redirect to the subdomain;
2) a way to keep WP from kicking me out of said subdomain.

Anything is *possible*, but no. I could send you down a long winding road to accomplish this, but it would lead you into more problems than you have already. My suggestion is to talk some more with your host. They need to be informed that you're running WordPress® ( which is NOT going to work with a separate SSL sub-domain ). Short of that, I highly recommend MediaTemple (gs).
http://mediatemple.net/webhosting/gs/

Just to note. WordPress® MUST be configured to operate on a specific domain through it's Settings -> General tab. So introducing a separate sub-domain just for SSL connectivity is throwing a monkey wrench into its intended functionality.

Please let me know if I can help further.
Feel free to report back with any solutions that you find.