Could not read from SSL socket: 'SSL read error' during account transfer

[Cio]

Hello,

We are transfering an acount by using the WHM transfer tool between two servers running CloudLinux...

We've been transferring a few sites in the last few days between two servers without any problem. But one account gives an error at the end of the transfer. I could not find any similar problem or any solution to this. It would be appreciated if you can help to solve this issue.

The error log is as below

Cpanel::Exception::HTTP::Network/(XID yuyzfc) The system failed to send an <abbr title="Hypertext Transfer Protocol">HTTP</abbr> “GET” request to “https://IPadress:2083/download/backup-2.25.2021_01-06-27_user.tar.gz” because of an error: Could not read from SSL socket: 'SSL read error'
at /usr/local/cpanel/3rdparty/perl/530/lib/perl5/5.30.0/HTTP/Tiny.pm line 1200.
at /usr/local/cpanel/Cpanel/HTTP/Client.pm line 115.
Cpanel::HTTP::Client::request(Cpanel::HTTP::Client=HASH(0x2f53650), "GET", "https://IPadress:2083/download/backup-2.25.2021_01-06-2"..., HASH(0x33172e0)) called at /usr/local/cpanel/scripts/getremotecpmove line 297
scripts::getremotecpmove::fetch_acct_by_cpanel(__CPANEL_HIDDEN__, __CPANEL_HIDDEN__, __CPANEL_HIDDEN__, __CPANEL_HIDDEN__, __CPANEL_HIDDEN__, __CPANEL_HIDDEN__, __CPANEL_HIDDEN__, __CPANEL_HIDDEN__) called at /usr/local/cpanel/scripts/getremotecpmove line 58
scripts::getremotecpmove::script("scripts::getremotecpmove", "IPadress", "user") called at /usr/local/cpanel/scripts/getremotecpmove line 31

Thanks

 

[cPRex]

Hey there! These are often tricky to troubleshoot without server access. Do you have root access to the Source machine? I ask because it shows port 2083, which isn't what I would expect to see during a transfer if that is being performed by the root user.

If you do have root access to both systems you can submit a ticket to our team and we'd be happy to check things. If your Source access is more limited, are you able to access the address of the Source machine at https://IPadress:2083? If not, that could also indicate a problem with that domain or SSL connection that would need to be resolved on the Source side of things.