Transfer from older WHM

jmartinmds

• April 03, 2026 14:54

I have a WHM server running 110.0.93 on Cloudlinux 7.9 that still has a few sites on it. For various reasons we want to simply move the sites off this server rather than elevate. When I go to a newer server running 134.0.13 and try to use the transfer tool, I put in all of the info and then it hangs on "Creating Session". I've tried the tool between two servers running 110 and two running 134 and it works in those cases, so the basic functionality is there, it's just crossing the version gap that seems to be the problem. Aside from moving the sites one by one is there any workaround for this?

• 

  jmartinmds

  • April 03, 2026 14:55

  If it makes any difference, the process I see is
  xml-api - create_remote_root_transfer_session
  I have to kill that process manually, it doesn't seem to time out (or I'm too impatient to wait if it's a long timeout)

  0
• 

  William Del Piero cPanel Staff

  • April 04, 2026 16:17

  Hi,

   

  The issue you reported can often be caused by network issues or authentication problems between the servers. Can you confirm if the destination server can connect to the source server on port 2087 and the SSH port? You can use the nmap tool to test this by running nmap on the destination server to scan the source server IP:

   

  How to use nmap to troubleshoot port connectivity issues

   

  If nmap shows either port as filtered, this can indicate a firewall block which can cause issues with the Transfer Tool. In that case, I'd recommend reviewing your firewalls on both servers to ensure that connections are allowed on port 2087 and the SSH port between the servers.

   

  Additionally, if you are using a password to connect, I recommend ensuring that password authentication is enabled in the source server's SSH configuration (/etc/ssh/sshd_config).

  0
• 

  jmartinmds

  • April 22, 2026 14:57

  Source (v110) and destination (v134) servers are both whitelisted in each others' firewalls. I can connect to the source server from another server that's also on v110, but not from any server running v134. Behavior is the same whether or not I have SSH password auth enabled on the source server.

  0

Please sign in to leave a comment.