Title: Export getting stuck at database
Last modified: May 19, 2026

---

# Export getting stuck at database

 *  Resolved [minamt](https://wordpress.org/support/users/minamt/)
 * (@minamt)
 * [2 weeks, 6 days ago](https://wordpress.org/support/topic/export-getting-stuck-at-database/)
 * Hello,
   I’m trying to export my website, but it gets stuck at 0% at database then
   shows me error: “Unable to export, Refresh the page and try again)Can you help
   me identify the issue?Thank you

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

 *  Plugin Author [Yani](https://wordpress.org/support/users/yaniiliev/)
 * (@yaniiliev)
 * [2 weeks, 6 days ago](https://wordpress.org/support/topic/export-getting-stuck-at-database/#post-18912556)
 * Hi there,
 * Sorry you’re running into this! An export that stalls at 0% on the database step
   usually points to one of a few common causes on the hosting side. Here are some
   things to check:
 * 1) Server resources
    – Memory limit: we recommend at least 256MB of PHP memory.
   Lower limits often cause the database step to fail right at the start. – Disk
   space: make sure you have more free space on the server than the expected size
   of the backup.
 * 2) Check the error log
    The plugin writes PHP errors and notices to: `wp-content/
   plugins/all-in-one-wp-migration/storage/error.log` Opening that file usually 
   gives a clear hint about what’s failing (timeout, memory, a transient/oversized
   table, a plugin conflict, etc.).
 * 3) Database-specific causes
    Large `wp_options` transients or very large custom
   tables can stall the database export. Clearing expired transients from your DB
   often helps. A plugin conflict can also interrupt the export. Temporarily deactivating
   other plugins and trying again is a good test. Use advanced options and skip 
   spam comments.
 * 4) Hosting limits
    Some hosts impose short execution time or request limits that
   kill the export early. If you have access to PHP settings, raising `max_execution_time`
   and `memory_limit` is worth a try.
 * There’s a general troubleshooting guide here that covers most of this: [https://help.servmask.com/knowledgebase/troubleshooting-2/](https://help.servmask.com/knowledgebase/troubleshooting-2/)
 * If you can share the contents of the error.log file and a rough idea of your 
   site size, I’d be happy to take another look.
 * Thanks!
 *  Thread Starter [minamt](https://wordpress.org/support/users/minamt/)
 * (@minamt)
 * [2 weeks, 6 days ago](https://wordpress.org/support/topic/export-getting-stuck-at-database/#post-18912606)
 * Hello,
   Thank you for the reply, I’ve already increased memory_limit and max_execution_time
   but still facing the same problem, here is the error I found on error log:
 *     ```wp-block-code
       May 19 2026 14:16:32{"type":8192,"message":"Return type of Ai1wm_Recursive_Newline_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice","file":"\/home\/roch9836\/repman.pro\/wp-content\/plugins\/All-In-One-WP-Migration-With-Import-master\/lib\/vendor\/servmask\/filter\/class-ai1wm-recursive-newline-filter.php","line":28}May 19 2026 14:16:43{"type":8192,"message":"Return type of Ai1wm_Recursive_Newline_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice","file":"\/home\/roch9836\/repman.pro\/wp-content\/plugins\/All-In-One-WP-Migration-With-Import-master\/lib\/vendor\/servmask\/filter\/class-ai1wm-recursive-newline-filter.php","line":28}May 19 2026 14:16:54{"type":8192,"message":"Return type of Ai1wm_Recursive_Newline_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice","file":"\/home\/roch9836\/repman.pro\/wp-content\/plugins\/All-In-One-WP-Migration-With-Import-master\/lib\/vendor\/servmask\/filter\/class-ai1wm-recursive-newline-filter.php","line":28}May 19 2026 14:17:05{"type":8192,"message":"Return type of Ai1wm_Recursive_Newline_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice","file":"\/home\/roch9836\/repman.pro\/wp-content\/plugins\/All-In-One-WP-Migration-With-Import-master\/lib\/vendor\/servmask\/filter\/class-ai1wm-recursive-newline-filter.php","line":28}May 19 2026 14:17:16{"type":8192,"message":"Return type of Ai1wm_Recursive_Newline_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice","file":"\/home\/roch9836\/repman.pro\/wp-content\/plugins\/All-In-One-WP-Migration-With-Import-master\/lib\/vendor\/servmask\/filter\/class-ai1wm-recursive-newline-filter.php","line":28}May 19 2026 14:17:27{"type":8192,"message":"Return type of Ai1wm_Recursive_Newline_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice","file":"\/home\/roch9836\/repman.pro\/wp-content\/plugins\/All-In-One-WP-Migration-With-Import-master\/lib\/vendor\/servmask\/filter\/class-ai1wm-recursive-newline-filter.php","line":28}May 19 2026 14:17:39{"type":8192,"message":"Return type of Ai1wm_Recursive_Newline_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice","file":"\/home\/roch9836\/repman.pro\/wp-content\/plugins\/All-In-One-WP-Migration-With-Import-master\/lib\/vendor\/servmask\/filter\/class-ai1wm-recursive-newline-filter.php","line":28}May 19 2026 14:16:32{"type":8192,"message":"Return type of Ai1wm_Recursive_Newline_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice","file":"\/home\/roch9836\/repman.pro\/wp-content\/plugins\/All-In-One-WP-Migration-With-Import-master\/lib\/vendor\/servmask\/filter\/class-ai1wm-recursive-newline-filter.php","line":28}May 19 2026 14:16:43{"type":8192,"message":"Return type of Ai1wm_Recursive_Newline_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice","file":"\/home\/roch9836\/repman.pro\/wp-content\/plugins\/All-In-One-WP-Migration-With-Import-master\/lib\/vendor\/servmask\/filter\/class-ai1wm-recursive-newline-filter.php","line":28}May 19 2026 14:16:54{"type":8192,"message":"Return type of Ai1wm_Recursive_Newline_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice","file":"\/home\/roch9836\/repman.pro\/wp-content\/plugins\/All-In-One-WP-Migration-With-Import-master\/lib\/vendor\/servmask\/filter\/class-ai1wm-recursive-newline-filter.php","line":28}May 19 2026 14:17:05{"type":8192,"message":"Return type of Ai1wm_Recursive_Newline_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice","file":"\/home\/roch9836\/repman.pro\/wp-content\/plugins\/All-In-One-WP-Migration-With-Import-master\/lib\/vendor\/servmask\/filter\/class-ai1wm-recursive-newline-filter.php","line":28}May 19 2026 14:17:16{"type":8192,"message":"Return type of Ai1wm_Recursive_Newline_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice","file":"\/home\/roch9836\/repman.pro\/wp-content\/plugins\/All-In-One-WP-Migration-With-Import-master\/lib\/vendor\/servmask\/filter\/class-ai1wm-recursive-newline-filter.php","line":28}May 19 2026 14:17:27{"type":8192,"message":"Return type of Ai1wm_Recursive_Newline_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice","file":"\/home\/roch9836\/repman.pro\/wp-content\/plugins\/All-In-One-WP-Migration-With-Import-master\/lib\/vendor\/servmask\/filter\/class-ai1wm-recursive-newline-filter.php","line":28}May 19 2026 14:17:39{"type":8192,"message":"Return type of Ai1wm_Recursive_Newline_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice","file":"\/home\/roch9836\/repman.pro\/wp-content\/plugins\/All-In-One-WP-Migration-With-Import-master\/lib\/vendor\/servmask\/filter\/class-ai1wm-recursive-newline-filter.php","line":28}
       ```
   
 *  Plugin Author [Yani](https://wordpress.org/support/users/yaniiliev/)
 * (@yaniiliev)
 * [2 weeks, 6 days ago](https://wordpress.org/support/topic/export-getting-stuck-at-database/#post-18912617)
 * Hi again, and thanks for sharing the log!
 * The log actually points to the real cause: the plugin you’re running isn’t our
   official All-in-One WP Migration plugin. Look at the file path in the error:
 * > /wp-content/plugins/All-In-One-WP-Migration-With-Import-master/lib/vendor/servmask/
   > filter/class-ai1wm-recursive-newline-filter.php
 * What I’d recommend:
 * 1) Deactivate and fully delete the `All-In-One-WP-Migration-With-Import-master`
   folder from `wp-content/plugins/`.
    2) Install the official plugin from WordPress.
   org:[https://wordpress.org/plugins/all-in-one-wp-migration/](https://wordpress.org/plugins/all-in-one-wp-migration/)
   3) Try the export again.
 *  Thread Starter [minamt](https://wordpress.org/support/users/minamt/)
 * (@minamt)
 * [2 weeks, 5 days ago](https://wordpress.org/support/topic/export-getting-stuck-at-database/#post-18913408)
 * Hello,
   I deleted the plugin, installed it from official wordpress.org, and tried
   the export again, it still doesn’t work and I couldn’t find an error log file

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

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fexport-getting-stuck-at-database%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](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/)

## Tags

 * [database](https://wordpress.org/support/topic-tag/database/)
 * [export](https://wordpress.org/support/topic-tag/export/)
 * [Stuck](https://wordpress.org/support/topic-tag/stuck/)

 * 4 replies
 * 2 participants
 * Last reply from: [minamt](https://wordpress.org/support/users/minamt/)
 * Last activity: [2 weeks, 5 days ago](https://wordpress.org/support/topic/export-getting-stuck-at-database/#post-18913408)
 * Status: resolved