SSL - A definitive answer

[Host4u2]

If you find you still have a problem... since all else is okay, just assign your abc.com a unique IP address, then uninstall the cert, and then reinstall via your WHM using the new unique IP. However, it sounds like all is well now

[fadedpictures]

So i just want to clarify.

I'm in a similiar situation.

i have just installed a cert on my main domain name under secure.mymaindomain.com for use as a shared ssl cert for my server. the IP address assigned to my secure.mymaindomain.com URL is different from the main shared IP address of the server.

All my shared virtual accounts are attached obviously to the main shared IP address of the server.

Do i need to get my cert reissued to the main shared IP address of the server? Instead of to my sites main IP address, which is only assigned to my site and the secure sub.

as of now i get a 404 error message when i try and go to https://secure.mymaindomain.com/~username/
and the only thing i can think of to fix the issue is to tie the cert to the servers IP addresss.

are certs bound to the ip, or just the name i.e. secure.mymaindomain.com?

thanks for you all your help.

Bret
faded pictures designs

[mweb]

Certs are only bound to the name. There's a lot of noise in these forums saying that certs are bound to IP, but that's entirely not true.

If you're doing this to leverage your one certificate, you should make sure that in httpd.conf it's the default virtual host for that ip. Then you should be able to use /~username all you want. Bear in mind that those users won't be able to run perl scripts unless the site is running as "nobody".

You might want to check that you've got ~username enabled under tweak security > mod_userdir (checked for "default").

[fadedpictures]

Thanks for the clarity on the issue, that helps a lot.