Skip to main content

Transfer Tool Failed to connect: Operation already in progress

Answered

Comments

21 comments

  • cPRex Jurassic Moderator

    Hey there!  It's almost always quicker to open a ticket than to post here if you have that option :D

    When I've seen this issue in the past it has been caused by a networking issue between the servers, as the SSH session starts but isn't able to complete.  Are you able to connect between the two servers manually over SSH outside of the Transfer Tool?

    0
  • Unnamed User

    Hello

    I have same error. (XID mxw9uk) The system failed to connect to “xx.xxx.xx.xxx” on port “xx” because of an error: Operation already in progress

    It all worked fine a day ago. Never had problem with transfer tool. I can not opet ticket beacuase i purchased licence over datacenter... i am trapped

    When i try to ssh over terminal in whm to old server i get can not resolve hostname.

    0
  • cPRex Jurassic Moderator

    I'd ask the same question for your situation - does a manual SSH connection work between the two servers?

    1
  • FourMat

    In my situation I found that the transfer tool created a firewall block on the other end.  I check the firewall, and whitelisted the new IP and never had a problem again.

    1
  • Unnamed User

    Yes, that was that. Whitelist solve the problem. I did whitelist new server in the old but didn't old in the new...

     

    I any way, thank you very much for responses. Much aprishiated.

    1
  • cPRex Jurassic Moderator

    I'm glad you found the issue within the firewall!

    1
  • Ben Taylor

    I have whitelisted the new ip address on the old server, rebooted both of them, but I still get `Operation already in progress`

    Even if I put the wrong port in it gives the same error. Seems like it is stuck.

    Are there any other solutions?

    0
  • cPRex Jurassic Moderator

    Ben Taylor - can you confirm the servers are able to talk to each other in general?  Running a basic connection test from the Destination server to the Source server such as "telnet source.server.ip.here 22" would show that.  Just ensure you use the correct IP of the source machine and SSH port and see if that works.

    0
  • Ben Taylor

    I had got one account transferred ok but using just username and password.

    This particular time I tried to use root and an ssh key.

    I have one more account to transfer and may just use the same way without root? The only reason I thought there was a problem was because I had already transferred one account, but thought it was still running because the error said `Operation already in progress`

    0
  • cPRex Jurassic Moderator

    I would say use whatever works - the "already in progress" error may not always be the most clear in every situation.

    0
  • Ben Taylor

    I can no longer transfer using just username and password. I know for sure that I have added the destination ip address on the source host to both CSF and cPHulk as when I added them they both said either comment updated or already added.

    telnet results

    telnet: connect to address xxx.xxx.xxx.xxx: Connection refused

    The error I get is connection refused as follows. Yeah I know "connection refused" mean the firewall is blocking the ip, but I can assure you the ip address is whitelisted

     

    `

    Starting “TRANSFER” for “Account” username.
    Attempting to copy username from “xxx.xxx.xxx.xxx”.
    Trying to fetch cpmove file via cPanel API!
    Failed to establish session and parse security token: 599 Internal Exception (Could not connect to 'xxx.xxx.xxx.xxx:2083': Connection refused
    )
    Failed to establish session and parse security token: 599 Internal Exception (Could not connect to 'xxx.xxx.xxx.xxx:2083': Connection refused
    ) at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/cPanel/PublicAPI.pm line 526, <STDIN> line 1.
    Failed: Error while executing “/usr/local/cpanel/scripts/getremotecpmove”. The “/usr/local/cpanel/scripts/getremotecpmove xxx.xxx.xxx.xxx ngwenyag” command (process 34317) reported error number 111 when it ended.: Failed to establish session and parse security token: 599 Internal Exception (Could not connect to 'xxx.xxx.xxx.xxx:2083': Connection refused ) Failed to establish session and parse security token: 599 Internal Exception (Could not connect to 'xxx.xxx.xxx.xxx:2083': Connection refused ) at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/cPanel/PublicAPI.pm line 526, <STDIN> line 1.`
    0
  • quietFinn

    Is the outgoing port 2083 (TCP_OUT in CSF) open?

    0
  • Ben Taylor

    2083 is missing on TCP_OUT on source server. However this tool worked two days ago with another account.

     

    0
  • quietFinn

    I just tested this, port 2083 must be open in the source server OR IP of the destination server must be in /etc/csf/csf.allow in the source server.

    0
  • Ben Taylor

    I have just added 2083 to TCP_OUT and restarted CSF. The destination IP address is also in /etc/csf/csf.allow. I am still getting connection refused.

    I have had issues with my current host digging their heels in with me moving. Could they issue a block at their level?

    0
  • quietFinn

    Can you connect from the source server to the destination server using telnet?
    telnet xxx.xxx.xxx.xxx 2083

    xxx.xxx.xxx.xxx is the IP of the destination server.

    0
  • Ben Taylor

    I cannot get a connection doing anything actually. So far all of the below are "connection refused" 

    ssh -p xx userg@xxx.xxx.xxx.xxx
    nc -vz xxx.xxx.xxx.xxx xx
    telnet xxx.xxx.xxx.xxx xx

    The only thing that does work is ping xxx.xxx.xxx.xxx!

    0
  • cPRex Jurassic Moderator

    It sounds like there is a firewall issue of some sort blocking the connection between the servers.  If you aren't seeing anything on your side you might need to speak with the host to have them check any external firewalls that may be in place.

    0
  • Ben Taylor

    you might need to speak with the host to have them check any external firewalls that may be in place.

    I'm concerned that they won't even check, as they often fall back on the 'unmanaged server' excuse. If they did investigate and found an issue, it would essentially help us move away from their services.

    0
  • cPRex Jurassic Moderator

    If the only thing that works is ping *and* you've already confirmed the firewall is open or disabled on both machines, that really isolates the issue to something outside of your system's control.

    0
  • Ben Taylor

    The one thing we did not try was to disable the firewall on both servers and now it has started. Whoops!

    Thanks for your time.

    0

Please sign in to leave a comment.