Support

Akeeba Backup for WordPress

#28163 – Site Transfer Wizard won't upload files to new server

Posted in ‘Akeeba Backup for WordPress’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Monday, 24 July 2017 14:02 CDT
starcontinuum
Hi there... let me give you a short summary:

What i have:
- Knowledge of AkeebaBackup Core since couple of years
- Managed Server running on 1und1/Germany
- A complete WordPress site, often backuped and restored via Kickstarter
- Admin FTP/SFTP
- Default Backup Profile for complete site
- Working Backup in my own Backup folder

What i do:
- Click Site Transfer Wizard
- Working Connection to new Site
- hitting "Proceed with restoration" button

What Site Transfer Wizard does:
- Validating
- Successful uploading Kickstart
- Trying to upload Backup
- Error: Akeeba Backup for WordPress cannot upload the backup file ... It's possible that your new site's server has ran out of disk space or a server protection is blocking the transmission of the data. Please try transferring your site by selecting the Manually transfer option. Do note that files have been left behind on your new server; you may want to remove them manually.

I tried all options like FTP, SFTP, cURL, native PHP functions. Same results. Tried it with 2.2.0 as well as with 2.1.3 - same results. When i add another Backup profile, same result. When i limit the part-file sizes to 5MB in my default Backup Profile, the Site Transfer Wizard starts to transfer via FTP, but it stops after 4.6% with an Error (500)...


My Workaround:
When i add another profile with Post Processing Engine: Upload to Remote FTP and include Kickstart, the transfer is done and i can start installing the new page.


My Question:
I don't understand the difference between "Site Transfer Wizard" and "Backup with Upload to Remote FTP". I think i have no effectable limits or restrictions on my server. So where could be the problem?


I just bought the PRO version today because of the Site Transfer Wizard, and now exactly this is not working. It's a bit of frustrating...


Thanks for your help and kind regards
Rafael

Custom Fields

WordPress version (in x.y.z format) 4.8
PHP version (in x.y.z format) 7.1.7
Akeeba Backup version (x.y.z format) 2.1.3 / 2.2.0
Tuesday, 25 July 2017 01:42 CDT
nicholas
I don't understand the difference between "Site Transfer Wizard" and "Backup with Upload to Remote FTP". I think i have no effectable limits or restrictions on my server. So where could be the problem?


Upload to Remote FTP is a post-processing engine. After the backup is complete, Akeeba Backup connects to your remote FTP server and uploads one backup part at a time. You can also copy Kickstart if you check that box in Akeeba Backup's Configuration page. The downside is that if you try to upload a large file (typically over 10Mb, depends on your web server where the backup is running, the remote FTP server and the transfer speed between them) you can run into a timeout error and the transfer will fail.

Site Transfer Wizard (STW), on the other hand, works separately from the backup. It needs a backup to have already been taken. First it uses FTP or SFTP to upload Kickstart itself to the remote server, along with an add-on Kickstart feature. The add-on feature allows Kickstart to operate as an uploads manager. Then STW will send a POST request to the remote copy of Kickstart with an 1Mb chunk of the backup archive. The remote copy of Kickstart will put it in a temporary directory. When all 1Mb chunks of a backup part have been received, the remote copy of Kickstart will assemble the part file and store it alongside kickstart.php. Rinse and repeat for all archive parts and now you have your backup on the remote server, circumventing the large upload issue of Upload to Remote FTP.

The problem is that not all web servers will allow you to use this method. Some servers apply limits on how much data you can upload, or filter POST requests, or don't like uploads not originating from browsers, or... You get the idea. This is what happens in your case. The remote server does not like STW's method of safely uploading files. Therefore using Upload to Remote FTP is the best option at your disposal.

I just bought the PRO version today because of the Site Transfer Wizard, and now exactly this is not working. It's a bit of frustrating...


I think you have it backwards. STW is available in both Core and Pro versions. Upload to Remote FTP, though, is only available in Akeeba Backup Professional. So what you bought actually allows you to transfer the site, whereas using the Core version wouldn't (because of your server's issues).

In fact, if you use the Upload to Remote FTP with the Upload Kickstart option enabled you have the identical functionality of Site Transfer Wizard. After all, STW's job is to upload the backup archive and Kickstart to the remote server.

As I tried to explain, there are two different ways to accomplish that (STW and Upload to Remote FTP/SFTP) because not all servers are compatible with just one of these methods. Most servers support both. Quite a few servers only work with the STW. A few other servers (like yours) only work with Upload to Remote FTP. And yes, there are very very few servers which don't work with anything and are a pain to manage anyway - but there's nothing we can do about that.

Overall, I think you are on the right track with the self-administered solution to your problem. You are using the correct Pro-only feature to perform a site transfer.


Nicholas K. Dionysopoulos

Lead Developer and Director



🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



Tuesday, 25 July 2017 02:33 CDT
starcontinuum
Hi Nicholas,

thank you for your reply and explanation... i understand the difference now as well as the problems with the Site Transfer Wizard transfers...

I used Akeeba since ages and i was always a fan... don't get me wrong, i am not frustrated that i subscribed to pro - i was just frustrated, it didn't work like i expected. And because of my long-years-using of Akeeba, i will keep the Pro in the future. By the way i even didn't try the STW before in the Free version, cause there was no need so far and i really thought it is just a Pro feature...

Keep on going with this great PlugIn, and as i found my way to get the transfer done anyway without doing it complete manually, i am happy with it.


Kind regards
Rafael
Tuesday, 25 July 2017 02:37 CDT
nicholas
I'm glad I could help clarify the differences between these methods :)


Nicholas K. Dionysopoulos

Lead Developer and Director



🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.

Support Information

Working hours: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!