Method 1

  • Resolved vilo1968

    (@vilo1968)


    3 weeks, 1 day ago

    Hi again,

    I performed some additional testing on a public website (not an intranet), and I found another issue that seems to be related to Method 1.

    Here are the results:

    • The website is publicly accessible.
    • It uses Wordfence.
    • Initially, Wordfence reported a false positive for one of the Backup Migration AJAX requests. I accepted the suggested allowlist rule.
    • I tried creating another manual backup using Method 1, but it failed again.
    • To completely rule out Wordfence, I disabled the Wordfence plugin and tested Method 1 again. It still failed.
    • Then I switched Backup Migration to Method 2, and the manual backup completed successfully.

    I also reviewed the generated log and found something interesting.

    The backup process actually starts and later reports:

    “Backup file created successfully via backup-process.php”

    However, during Method 1 the frontend AJAX request receives a 404 response containing the full HTML of the website’s 404 page, instead of the expected AJAX response. After that, several AJAX requests report “NetworkError”.

    This makes me think that the backup itself is actually being created, but the frontend reports it as failed because one of the AJAX requests unexpectedly returns a 404 page.

    Could you please check whether this is a known issue with Method 1?

    Debuge code: BMI-4BSCbO48-72012

    Thank you!

Viewing 1 replies (of 1 total)
  • Plugin Support MixHa

    (@mixha)

    1 week, 5 days ago

    Hi @vilo1968 ,

    Thank you for the detailed investigation and for sharing the debug code. It was very helpful.

    From what you described, this is actually the expected limitation of Method 1 rather than a new issue.

    Method 1 performs the backup work within a single HTTP request. On some hosting environments, long-running or resource-intensive requests are terminated by security systems such as ModSecurity, web application firewalls, or other hosting-level protections. When that happens, the frontend may receive a 404 or another unexpected response, even though the backup process itself had already started and may have partially or fully completed.

    Method 1 is intended primarily for either:

    – Smaller websites where the entire backup can complete within a single request.
    – Servers where PHP CLI is available and correctly configured in the plugin settings, allowing the actual backup process to be delegated to the CLI instead of running inside the web request.

    For larger websites or hosting environments with stricter limits, Methods 2 and 3 are generally much more stable and reliable, as they are specifically designed to avoid these limitations.

    This is also why we included the usage recommendations in the tooltip next to each backup method.

    Based on your testing, Method 2 appears to be the best choice for your hosting environment.

    Thanks again for taking the time to investigate this and provide such detailed feedback – it is greatly appreciated.

    Kind regards

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.