Migration and NAT
Hello,
I have an existing installation that is connected directly to the Internet.
I wish to migrate it to a new server, but soon after the migration I wish to change so the server will be behind a firewall.
I saw this NAT article
strongly recommend that you only perform these actions on a new installation of cPanel & WHM. Do not attempt a 1:1 NAT configuration on an existing production server.
"
So I don't know what is the correct order of doing it, like:
1. Install a new server, migrate to it and then fw and NAT? not good, you asked to setup NOT on non-prod
2. Install the new server, NAT it with FW and then Migrate via the FW?
3. Something else?
Thanks.
-
Begin by configuring your 1:1 NAT after the operating system installation, and proceed to install cPanel/WHM then migration. 0 -
Is there a particular reason why you want to put the server behind a firewall after the migration? cPanel and the migration tools will work just fine as long as the appropriate ports are open in the firewall. 0 -
Currently, the "old" production, is directly connected to the Internet with local firewalld. I have to move CP to another server as CP don't support centos anymore. The other thing is that I wish to "outsource" the fw function to a dedicated fw virtual device, for a more convenient management and disable the local firewalld on cpanel. Two "jumps" to do. I prefer, it looks to me more logical, to setup the fw with the new, fresh, CP server, and then do the migration. 0
Please sign in to leave a comment.
Comments
3 comments