What Can We Help You With?
Choose Your Product
Frequently Asked Questions
- If you receive an error for Autorization, such limitation may be implemented by your bank for security reasons. Sometimes they reject payments to US based companies. Please contact your bank to fix the issue. We would also like to inform you that 2Checkout supports PayPal too. In case you have a Paypal account you can use it too.
- If you don't receive any error message, likely this is an issue related to the browser you're running. Try to use another browser to see if the issue still there?
- First of all, enable Do backup with reloads option in your settings section, then try to keep the browser window open while there are on going backup or restoration procedures. Generally this approach resolves this issue!
- Try to disable Do backup with reloads option in your settings section to see how this affects.
- If you have a security plugin installed on your website, try to disable it to make sure it doesn't prevent/stop the backup procedure.
- Finally, contact your hosting provider and ask them to increase that configuration for you. Almost all hosting providers do this upon customer request.
The reason varies depending on the server and WordPress configurations. We don't have sufficient access to your resources to figure out exactly what's the cause. So, you can check the following:
Look for a line like this in your wp-config.php file (which is found in the root directory of your WordPress installation), and remove it (or change true to false, making sure there are no quote marks around false):
Is your website in maintenance mode? This disables all kind of scheduled tasks – so turn it off first.
WordPress' scheduler relies on the site having visitors. No visitors means that WordPress doesn't run, and therefore can't hand over to the scheduled task. If your site is in development, and you schedule a backup run for a time when all the developers are asleep, then that may be the cause for the scheduled tasks not running.
Some web hosting providers (one big example: Heart Internet) purposefully (though for no good reason) disable the "loop-back" connects that allows WordPress to run its scheduler. If loopback connections are not working (whether deliberately disabled or not), you can try to use the alternative scheduling system of WordPress – instructions here: https://codex.wordpress.org/Editing_wp-config.php#Alternative_Cron. The instructions amount to one thing: add a line anywhere in the middle of your wp-config.php file as follows (don't add it too late in the file, or it will take no effect):
When your website is down and you don't have access to your dashboard, you have two options for restoration:
1. WordPress re-installation
- Install a new/clean WordPress instance
- Install BackupGuard plugin
- Import the backup you want to restore
- Restore and you're done!
2. Manual restoration
- First of all, you should extract your archive. More information regarding this can be found here: https://help.backup-guard.com/en/article/extract-sgbp-archive-hwyeo1
- Connect with FTP client (e.g. FileZilla or Cyberduck) and upload the extracted wp-content directory on your server
- Now using cPanel tools (e.g. phpMyAdmin), import your database SQL file
- After importing the SQL file, find what's your database table prefix
- Now open the wp-config.php file and make sure the table_prefix is the same as imorted in your DB
Website backup or restoration is a complex process which may take a couple of minutes depending on many circumstances. When the allocated time is not sufficient to complete the process, the backup or restoration ends up with execution timeout exception. This topic covers how to set up LiteSpeed web server so that a long running script will not be interrupted before it has finished.
Adding this in an early position in the .htaccess file in your WordPress root folder may fix the problem:
<IfModule Litespeed> RewriteEngine On RewriteRule .* - [E=noabort:1] </IfModule>
- the server timed out and closed the connection
- server dropped an incorrect or too large packet