• Resolved spoulios

    (@spoulios)


    Debug code: BMI-BzEXBsoW-93107

    I’ve already tested with disabling php cli which is shows in logs when starting, however it keeps failing.

    Also often after saving the option and going back after a while, the setting is enabled again.

    Any help?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author iClyde

    (@iclyde)

    Hi @spoulios

    As your website has error logging disabled, our plugin was unable to receive proper error, instead all I see is standard WP message “there was an error on the site […]”.

    The issue happens when our plugin tries to prepare list of files that will be included within the backup. As it’s first such report, I believe the issue may be specific to your site but we would like to resolve it in case as there can appear more such cases in future.

    My first assumption would be Jetpack plugin which can play some role in permission management, but there’s nothing much I can help if you’re on managed hosting.

    1. Please try to disable Jetpack plugin and try again, if it will work, you got the answer and we can’t do much in this case, nevertheless we will continue to test our plugin with Jetpack even if it highly conflicts with our plugin.
    2. If it’s still the same with Jetpack plugin disabled, you can enable it back
    3. Then go to wp-config.php file open it and enable WP_DEBUG and WP_DEBUG_DISPLAY constants, which will allow your site to display errors.
    4. Once you do that, try to make new backup and even if it fail it should contain details (in new debug code) which will allow me to provide you further help and solution.

    The error seem to be “critical” for the site which kills our process as well.

    Let me know if you can do that for me 🙂
    Thank you!

    Thread Starter spoulios

    (@spoulios)

    Very strange. It was indeed the Jetpack plugin that caused the original error. This time it went through and it seemed as if everything was fine (almost finished) until I looked back and got an error.

    This time the code is BMI-huzaJWqt-26866.

    Could you have a look? Debugging was enabled before running it again.

    Plugin Author iClyde

    (@iclyde)

    Hi @spoulios

    I can confirm that now I don’t see any fatal errors caught by our plugin, but at the same time it’s an issue.

    As you noticed the process didn’t finish and there were no error displayed. In the version you used we have browser error handler as well, but it was not initialized.

    My assumption is that something blocked our browser error handler as well as continuation of the process, and the reason may be LiteSpeed server which significantly limits your server performance.

    Overall it’s usually easy to increase limits if you have access to LS dashboard or cPanel.

    In your case seem like there are three/four possible reasons (or all at once):

    1. Your server has limited I/O (read/write speed on drive), in such case you need to remove that limit, it will make your website much incomparable faster as well.
    2. You can also try to increase max_execution_time in your php.ini to at least 300 seconds
    3. Increase Timeout and “Max Keep-alive Timeout”, “Max Keep-Alive Requests” and “Connection Timeout” in your LS config, set respectively at least 300, 1000 and 300
    4. Not enough space, but it’s very unlikely, in any case possible as I noticed similar results on sites where the hosting provider does not display real free space value.

    Read more about LS KeepAliveTimeout: https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:keep_alive

    You can compare how quick our plugin work on https://tastewp.com which is environment without LiteSpeed. Here you can backup 600 MB site even within few seconds.

    Let me know if you can modify mentioned configs, over all it should be enough to just resolve the first issue with I/O, it would automatically make our backup process quick enough to fit your current limits and resolve the issue. You may find more details in LS logs.

    Thank you!

    Plugin Support MixHa

    (@mixha)

    Hello @spoulios ,

    We haven’t heard from you since, so I’ll assume that the issue is resolved and will close this support ticket. If you face any new issues, please feel free to open a new ticket.

    Kind regards

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

The topic ‘Browser-side error when trying to take backup’ is closed to new replies.