[Snapshot Pro] Snapshot Is Not Creating Backups

We are trying to create backups for our sites. However, we keep getting a "max_execution_time" error and a "php zip module not found" error. Please view the following screenshot for more details:
We would like to understand how to remedy the issue or how to get the problem fixed. We are unable to make backups for our sites.

  • Nahid
    • Tech Support

    Hey Networking Bizz Digital !
    Hope you are having a great day!

    The above-mentioned warnings refer to the minimum prerequisites for Snapshot Pro to work, that aren't available within your server. Snapshot Pro requires PHP's max_execution_time in your server to be at least 180 seconds, which is set to 30 at the moment. Moreover, PHP's Zip module needs to be enabled in the server for Snapshot Pro to work correctly.

    The best way to overcome these is to get in touch with your host and request them to increase the PHP max_execution_time and enable the PHP Zip module. However, if you prefer to try that yourself, you can refer to this article for PHP max_execution_time and this article for PHP Zip module.

    Hope this helps. Let us know if you need any further assistance regarding this. Thanks!

    Kind regards,

  • Networking Bizz Digital
    • New Recruit

    We increased the maximum upload and PHP memory limit and enabling PHP zip archive module to clear the error for Snapshot Pro. However, this seemed to only work for one website (www.kweiquartey.com), and even then it did not seem to back up the site completely. The backup file is small, only 5 kb, which does seem to accurately reflect the size of the website.

    For another website (www.loadedcafe.com), the errors cleared. However, Snapshot Pro does not create a full backup. When the progress bar reaches 73%, it no longer progresses and after some time, the page bugs and we are left with "404" error. When we refresh the error clears, but no backups are made and the process begins again.

    For yet another website (www.newasiainconline.com), the "max_execution_time" error does not clear even after modifying the php.ini file, wp-config file, and .htaccess file.

    We would really like to get to the bottom of this to continue using your Dev Dashboard.

  • Nahid
    • Tech Support

    Hey Networking Bizz Digital !
    Hope you are doing well today!

    I'm extremely sorry to hear about the issues that you encountered. I wasn't able to replicate the reported issue in test sites of ours, so I believe it is something specific to your site. Could you please go through the following troubleshooting tests which would help us determine the source of the issue?

    1. Plugin/theme conflict test: Try running a full plugin/theme conflict test just to make sure no other plugin(s)/the theme on your site is/are conflicting with Snapshot Pro and thus causing the issue. The basic concept is to temporarily disable all the plugins except Snapshot Pro and WPMU DEV Dashboard, switch to a default WordPress theme and check if the issue still persists. If it doesn't, please enable all plugins and the theme one after another to see activating which brings back the issue. This handy flowchart can help you do a full plugin/theme conflict test.

    2. Enable debugging: If the plugin/theme conflict test doesn't help, please enable WP_DEBUG. You can enable debugging by putting the following constants in the wp-config.php file:

    // Enable WP_DEBUG mode
    define( 'WP_DEBUG', true );
    // Enable Debug logging to the /wp-content/debug.log file
    define( 'WP_DEBUG_LOG', true );
    @ini_set( 'log_errors', 1 );
    // Disable display of errors and warnings
    define( 'WP_DEBUG_DISPLAY', false );
    @ini_set( 'display_errors', 0 );
    // Snapshot Backtrace
    define( 'SNAPSHOT_BACKTRACE_ALL', true );

    These constants must be added before the line "/* That's all, stop editing! Happy blogging. */" for them to work. Please make sure identical constants are replaced if they were already there previously.

    Enabling debugging in WordPress will log any errors that the site encounters in a log file named "debug.log" located in the "wp-content" folder. Please upload the debug.log file in a cloud storage platform like Dropbox and attach the shared link in your next response so that we can take a look into it. You can know more about WordPress debugging in this handy article.

    Note: It is highly recommended that the site is backed up in an alternative way before the tests or the tests are done in a cloned staging site.

    3. Send credentials: If none of the above help, could you please send us the access credentials to your site and server so that we can take a closer look at the issue? You can send that privately through our secure contact form: https://premium.wpmudev.org/contact/#i-have-a-different-question

    Send in:

    Subject: "Attn: Nahid Mohit"
    - WordPress Admin Username
    - WordPress Admin Password
    - Login URL
    - FTP/cPanel credentials to the site files (host/username/password)
    - SFTP credentials to the Snapshot destination (host/username/password)
    - Link back to this thread for reference
    - Any other relevant URLs

    Hope this helps. We'll be looking forward to hearing back from you. Thanks!

    Kind regards,

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.