Database Errors

Unable to proceed because of a SQL query error OR Unable to proceed because ______ table exists.

Typically, the reasons for a table failing to get created is that one already exists with that name. Check your database to see if there is a duplicate of this table or if there is a table that is similiarly named with possibly just a difference in capitalization. As an example, wp_posts and Wp_posts. To help fix this, try dropping the offending table from your database and running the restore again.

Unable to restore the table______ due to existing foreign key constraints

VaultPress detected tables that have FOREIGN KEY constraints. The one-click restore feature does not currently support restoring such tables.

Database tables which use FOREIGN KEY constraints are usually created by plugins, like WooCommerce. If this is the case we recommend one of the following options:

  1. If you’re comfortable manually restoring your database, then we recommend doing so. You can restore everything but your site’s database using a one-click restore, and then restore the database afterwards by following the “Importing SQL Files” steps at Knowledge of CLI, phpMyAdmin or equivalent is required.
  2. You can run a single-file/table restore, which is outlined here. This method allows you to restore specific files, or database tables, rather than the site as a whole and is helpful for working around FOREIGN KEY constraints.
  3. Finally, we can enable an option that will tell VaultPress to ignore FOREIGN KEY constraints, which will allow a one-click restore to complete. Note: this is only recommended if the database table(s) in question will be repaired after the restore, or if you know that you’ll never use the table(s) in question.

500 Internal Server Error

This error indicates that something is going wrong with your server. Please contact your host in this event for more information.

If at any point you have questions, just contact us