Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I currently have a secured site running at and the certificate is bound to I also have a new version of the site running at If I use the current certificate on the new site, I will get the following warning from Google Chrome:

You attempted to reach, but instead you actually reached a server identifying itself as

What are the steps that I should take to get a new certificate for my new site? Should I:

  1. Re-generate a new public/private key pair
  2. Send the new public key along with the new distinguished name to a CA to get a new one

What are your thoughts?

share|improve this question
up vote 2 down vote accepted

If your CA will do you a multisite certificate for a sensible amount of money, you should attempt to get the certificate reissued with multiple names. However, on the basis that they're separate vhosts on separate SSL IP addresses, generating a new key and CSR and buying another certificate is a perfectly valid option.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.