Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

Is there a way to mitigate any issues? What should I consider when migrating servers?

share|improve this question
up vote 3 down vote accepted

So long as both servers have a valid certificate for the domain (even the exact same one on both), and so long as everyone is still accessing the site via the domain name (i.e. going to as opposed to, the SSL certificate is not affected, and neither is the user experience.

In fact, hosting your site on two different servers, each with the same certificate, while awaiting the DNS change to move from one to the other is probably the most transparent and user-friendly way to migrate servers -- 99.9% of your users simply will not know the difference (provided there's no errors or anything on the new server, of course).

share|improve this answer
Thanks. Odd I had read somewhere that you couldn't do so. Am trying to find that very same article. Anyhoo, does this mean that even if go back to same vendor that I had purchased the SSL certificate from for the same domain, it would not be an issue. Secondly does the SSL authentication not get fed back to the Certificate Authority? – PeanutsMonkey Jul 20 '11 at 23:02
Here is an article I came across – PeanutsMonkey Jul 20 '11 at 23:06
@PeanutsMonkey The key part is what your clients use to connect to your service. If they're using IP, then probably not. If they're using a FQDN, it should work just fine. – sysadmin1138 Jul 20 '11 at 23:15
@PeanutsMonkey The simplest solution is to just copy the certificate you have already put on your first server over to your second -- no need to buy a new one (assuming, as sysadmin1138 points out, your users are using the FQDN). If you do, for whatever reason, decide to buy a new certificate for the second server, you can buy it from any vendor -- no need to go back to the same one. As far as the CA is concerned, they've approved the certificate, not the server per se, so moving it around to a different server doesn't need to go back to them at all. – Kromey Jul 20 '11 at 23:32
@sysadmin1138/Kromey - Thanks. So I can assume safely that the certificate is bound to the FQDN and not an IP address unless I have specifically bought the SSL certificate for an IP address? – PeanutsMonkey Jul 20 '11 at 23:36

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.