• 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!

You must be logged in to reply to this topic.