Title: Failed &#8211; Network Error
Last modified: July 16, 2021

---

# Failed – Network Error

 *  Resolved [gabybitar](https://wordpress.org/support/users/gabybitar/)
 * (@gabybitar)
 * [4 years, 10 months ago](https://wordpress.org/support/topic/failed-network-error-4/)
 * Hi! I just updated to your new version of the plugin and trying to export to 
   file and once it gets to 650mbs I get the Failed – Network Error. Our backup 
   is 1GB and have exported it many times and never faced this issue before.
 * Please advise and what can we do to resolve this issue? Is there a bug in the
   new update or just coincidence?
 * Thanks

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Author [Yani](https://wordpress.org/support/users/yaniiliev/)
 * (@yaniiliev)
 * [4 years, 10 months ago](https://wordpress.org/support/topic/failed-network-error-4/#post-14669267)
 * It is a network error meaning that either:
    1. Your internet connection stops
   at some point and you can solve this by using a download manager like uGet 2.
   Your hosting provider has set a limit on the download and you can download files
   up to 650M. The solution sometimes is to use a download manager or to download
   the file via FTP from wp-content/ai1wm-backups folder.
 *  [LukDvr](https://wordpress.org/support/users/lukdvr/)
 * (@lukdvr)
 * [4 years, 8 months ago](https://wordpress.org/support/topic/failed-network-error-4/#post-14879200)
 * I’m having the same issue. Started all of a sudden. We have been downloading 
   a backup every day for the last several years with no issues. Our website is 
   about 4gb in size. Me and the content administrator have both tried downloading
   using Chrome and it is suddenly much slower and stops at around 200mb. I’m attempting
   to download via FTP currently but its not ideal.
 *  Thread Starter [gabybitar](https://wordpress.org/support/users/gabybitar/)
 * (@gabybitar)
 * [4 years, 8 months ago](https://wordpress.org/support/topic/failed-network-error-4/#post-14879207)
 * [@lukdvr](https://wordpress.org/support/users/lukdvr/) I found a workaround that
   works for us. Run the export the same way you have been, then log in via FTP 
   and goto /wp-content/ai1wm-backups/ and find the most recent backup file and 
   download via FTP
 *  [LukDvr](https://wordpress.org/support/users/lukdvr/)
 * (@lukdvr)
 * [4 years, 8 months ago](https://wordpress.org/support/topic/failed-network-error-4/#post-14879425)
 * [@gabybitar](https://wordpress.org/support/users/gabybitar/) Thanks I tried that
   and it timed out. So that means it must be the hosting provider (GoDaddy), not
   the plugin. I’m so tired of dealing with them. But thanks for responding.
 *  Thread Starter [gabybitar](https://wordpress.org/support/users/gabybitar/)
 * (@gabybitar)
 * [4 years, 8 months ago](https://wordpress.org/support/topic/failed-network-error-4/#post-14882664)
 * [@lukdvr](https://wordpress.org/support/users/lukdvr/) Yeah agreed, I stopped
   using GoDaddy many years ago. They are absolute trash, they have great marketing
   but it stops there. All of their products are extremely glitchy and run terribly.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Failed – Network Error’ is closed to new replies.

 * ![](https://ps.w.org/all-in-one-wp-migration/assets/icon-256x256.png?rev=2458334)
 * [All-in-One WP Migration and Backup](https://wordpress.org/plugins/all-in-one-wp-migration/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/all-in-one-wp-migration/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/all-in-one-wp-migration/)
 * [Active Topics](https://wordpress.org/support/plugin/all-in-one-wp-migration/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/all-in-one-wp-migration/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/all-in-one-wp-migration/reviews/)

 * 5 replies
 * 3 participants
 * Last reply from: [gabybitar](https://wordpress.org/support/users/gabybitar/)
 * Last activity: [4 years, 8 months ago](https://wordpress.org/support/topic/failed-network-error-4/#post-14882664)
 * Status: resolved