Cloned Instance/node issue
Hello.
I cloned an instance and am not able to access the WHM on the cloned server?
Cloned server IP: 45.56.xxx.xxx
Original server IP: 45.79.xxx.xxx
I tried to log into the cloned server at https://45.56.xxx.xxx:2087
I powered down the Linode for the clone and updated the password then powered it back on but it's not allowing me to gain access; I also logged on google chrome Incognito, cleared cookies as well but same issue where I am not able to access WHM on the clone?
From what I found is, it seems if I keyin the password on the Original server, despite using the IP of the cloned server I am logged on the Original server no the clone.
How do I login to the Whm on the cloned server with its own password so I can add domains to the cloned server and be independent without effecting the Original server.
Best.
-
Are you able to login via SSH? If so try the following steps to update the config files with the new primary IP of the server:
Andrew N. - cPanel Plesk VMWare Certified Professional
Do you need immediate assistance? 20 minutes response time!* Open a ticket
EmergencySupport - Professional Server Management and One-time Services0 -
What Andrew said. In general, cPanel doesn't support cloning servers as the IP address is written to many different configuration files.
0 -
Hi Andrew/cPRex.
Thanks on your message. Can you help with some clarification. Do you mean that on my Linode when I clicked to clone a server it isn't possible to access it independently from its own IP separate from the original server because of all the changes in the configuration files are linked to the original server? And if one config is setup off then the server is most likely not repairable? Do i have the right.
I am able to access the Glish/webglish console but not the Whm with the new password that i added on the clone server which still doesnt make sence for me.
Best.0 -
That's exactly correct - while the Linode tools work fine to clone the server, they don't interact with any of the cPanel configurations in order to make the server work after the clone has happened.
0 -
Hi CPRex,
Can you check if I have it understood correct on how the cloning process works: I have an original server, and I want to test some changes without risking the stability of the system. To do this, I create a clone of the original server. After that, I make the changes to the original since all the logs only direct me to the original server anyways. If the changes are unsuccessful, and something goes wrong on the original server that I am editing, I can switch to using the clone instead after deleting the original.
What I see is that the cloned server even though it has its own Ip it was using the original server Ip. The key point is that the cloned server will have a different IP address from the original. So after I remove the original server wouldn't the clone stop working since the Ip was on the original server. Is this understanding correct, or is there something I'm missing?Appreciate you help.
0 -
That sounds correct to me - there is nothing pointing network traffic to that IP on the new server's network card without some magic happening on the backend. Ultimately, this is a question for Linode and how they handle the networking aspect of a cloned system.
0
Please sign in to leave a comment.
Comments
6 comments