shared SSL redirect issue

[andrew green]

Hello,

Just trying to install shared SSL through WHM.
Generated the certificate for xxx.com, which works fine, marked the certificated as shared, however whenever I goto https://www.yyy.com I am redirected to https://www.xxx.com

Any idea what I'm missing,

Thanks

[andrew green]

actually I wouldnt say redirected, the url stays as https://www.yyy.com, however the content is that of www.xxx.com

[ChrisRHS]

A shared SSL needs to be accessed using the account user name, for example, if you installed a cert on https://xxx.com, and wish to share this throughout your server, you would need to access https://yyy.com through https://xxx.com/~yyy(account user name), otherwise, you will receive ssl errors with your browser, as the ssl cert will be for xxx.com.

[andrew green]

Thanks ChrisRHS,

Hit that nail right on the head

[sneader]

A shared SSL needs to be accessed using the account user name, for example, if you installed a cert on https://xxx.com, and wish to share this throughout your server, you would need to access https://yyy.com through https://www.com/~yyy(account user name), otherwise, you will receive ssl errors with your browser, as the ssl cert will be for xxx.com.

Must be a typo, otherwise, this makes no sense.

If the cert was purchased for xxx.com, then the users would access it via https://xxx.com/~yyy -- not https://www.com/~yyy.

Right?

- Scott

[ChrisRHS]

Must be a typo, otherwise, this makes no sense.

If the cert was purchased for xxx.com, then the users would access it via https://xxx.com/~yyy -- not https://www.com/~yyy.

Right?

- Scott

Correct, it was a typo, and is now fixed

[StevenD]

Odd question time, but Is there anyway to access the ~xxxx/ accounts as subdomains of the main domain with the shared ssl

so that if the domain with the shared ssl was

https://xxxxxx.com

that the accounts on the srever could use

https://yyyy.xxxxxx.com

instead of

https://xxxxxx.com/~yyyy/

I just hate that ~ in the shared ssl url

Steven

[sneader]

Unless you get a wildcard SSL certificate (can you say EXPENSIVE?), then your proposal of using the subdomain will not work. When you get a cert, you have to specify if you want it for www.example.com, or just example.com, or maybe secure.example.com. Once you specify the correct FQDN, you cannot then just use it for yyyy.example.com, without throwing up SSL errors.

The point is... even if you could devise a way for it to function like you want, the SSL cert would still throw up errors because the FQDN doesn't match what your ordered the cert for.

- Scott

[eth00]

Unless you get a wildcard SSL certificate (can you say EXPENSIVE?), then your proposal of using the subdomain will not work. When you get a cert, you have to specify if you want it for www.example.com, or just example.com, or maybe secure.example.com. Once you specify the correct FQDN, you cannot then just use it for yyyy.example.com, without throwing up SSL errors.

The point is... even if you could devise a way for it to function like you want, the SSL cert would still throw up errors because the FQDN doesn't match what your ordered the cert for.

- Scott

Wildcards have come down in price: http://www.rapidssl.com/ssl-certific...ertificate.htm
$199 there

I really thought I have seen them cheaper elsewhere I just cannot remember off hand. They are not that unreasonable anymore though.