Avoid service interruption by migrating a website protected by cloudflare

I have a domain name that points to a VPS, and I will soon migrate the site to another VPS. So I was wondering, is it the right procedure if I change the pointing IP in DNS, keeping the cloudflare protection, will the SSL generation on the new server work?

It seems like the same (or more) amount of work.
With no real added benefit - that I can see.

As I see it now:

  • client > DNS > serverA [IP]
  • client > DNS > serverB [IP] <<< CHANGE #1

Using CF (temporarily):

  • client > DNS > serverA [IP]
  • client > DNS > CF > serverA [IP] <<< CHANGE #1
  • client > DNS > CF > serverB [IP] <<< CHANGE #2
  • client > DNS > serverB [IP] <<< CHANGE #3

Using CF (permanently):

  • client > DNS > serverA [IP]
  • client > DNS > CF > serverA [IP] <<< CHANGE #1
  • client > DNS > CF > serverB [IP] <<< CHANGE #2

In summary: I don't see how CF can save any steps nor provide any consistency while back servers are being changed.
Unless, the entire site can be cached by CF.
OR
If CF can connect to multiple backends simultaneously.
[I don't use CF, so that might be a use case for you]
Which would look something like:
Using CF (temporarily with multiple backend servers):

  • client > DNS > serverA [IP]
  • client > DNS > CF > serverA [IP] <<< CHANGE #1
  • client > DNS > CF > serverA [IP] / serverB [IP] <<< CHANGE #2
  • client > DNS > CF > serverB [IP] <<< CHANGE #3
  • client > DNS > serverB [IP] <<< CHANGE #4
3 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.