Support

The remote server denied the connection at some point. This may be caused by a temporary routing issue between the two servers (source and destination) or by the destination server implementing a limit on the number of FTP connections you can create in a finite period of time.

There is an alternative to using the Site Transfer Wizard. Create a new backup profile and set it to be of the "Full site backup" type (default). Find the Archiver Engine row and click on the Configure button next to it. Set the "Part size for split archives" to 5Mb. In the Data Processing Engine row select "Upload to remote FTP server" and click on Configure. Give your FTP connection details. Then take a new backup.

This will create a regular backup in split files (.jpa, .j01, .j02 and so on) and automatically transfer them to your new site via FTP. Now upload kickstart.php to the new site's server and run it, i.e. visit http://www.example.com/kickstart.php (where www.example.com is your new site's domain name) in your browser. You can now extract the archive and proceed with the restoration.

This method is more reliable because it has to transfer less files. Instead of transferring all the 5,000+ files of your site it will only transfer a handful (most sites: 10-100) of archive part files. Kickstart extracts them on the target server. The rest of the procedure is common in both methods: Akeeba Backup Installer –the restoration script embedded by Akeeba Backup in all backups– is launched and allows you to restore your site's database on the new server.

You're welcome!