Thanks khiltdThe domain name on the certificate needs to match the domain name you're using to access cPanel.
As khiltd said, you supply the name when you order your certificate. I have no idea how you do it with the company you used, but it should have asked when you purchased the certificate.There's no "usually" involved, really; when you buy (or create) a certificate you supply one name.
//editIt seems equally unusual that you keep asking the same question no matter how many times it's answered. The two chunks of text you painted over in your screenshot need to match if you want to make that dialog go away. Nobody can give you any more specific instructions unless they can read what's currently there.
I'm about to kick the dog. It, "using the server name" works with FF but not IE7 and undoubtably a good numer of people will use IE.LeMarque,
It's not any different. If you access cPanel using the server name like you just said then you won't get the error. If you or a client of yours tries to access it via a domain name hosted on your server then it will come up. It's not that big a deal you just hit ok and keep on going.
And another just to say, because I have my own paranoid reasonsThis isn't so much a technical problem as it is a reading comprehension problem. If you want a more specific answer then post a legible screenshot and someone can walk you through the process step-by-step.
when I first signed up; I'm at a loss to see how its possible even with a wildcard cert for my hostname since its a shared ip.Main VPS IP Address:
"thay" don't know or care what your IP is, Apache and the user's browser do. The purpose of SSL certificates is security, and if it were possible for any host to masquerade as any other host they liked then they would be utterly useless and no one would bother.If a certificate (any of them) require a dedicated ip (how do thay know that its a dedicated ip anyway)