wp_remote_post() test back to this server failed! Response was: 404 Not Found

  • Resolved insightdes

    (@insightdes)


    6 years, 4 months ago

    Hi Folks,

    I have two sites on the same server: https://www.example.com.au & staging.example.com.au

    Both sites’ scans fail, and in both sites’ Tools > Diagnostics I see:

    wp_remote_post() test back to this server failed! Response was: 404 Not Found

    I have tried setting scans to start remotely but the same issue persists.

    How do I resolve this please?

    Thanks,
    Steve

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter insightdes

    (@insightdes)

    I remembered I have /wp-admin/.htaccess blocking all IPs except our own.

    I edited it to:

    order deny,allow
Allow from xxx.xxx.xxx.xxx
Allow from 69.46.36.0/24
deny from all

    If you can improve on Allow from 69.46.36.0/24 please let me know.

    Thanks,
    Steve

    Hi @insightdes,
    wp_remote_post() test attempts to make a POST request to wp-admin/admin-ajax.php on your server. Your server is apparently returning a 404. This isn’t something we can fix on our end, you’ll need to investigate why your server is returning a 404 on admin-ajax.php when your site tries to fetch it from itself. If it was a deny directive that was causing it, the response should probably have been 403 not 404?

    To sum up, when your site requests wp-admin/admin-ajax.php from itself, your site must serve it. It may need whitelisting your own servers IP.

    Hi @insightdes,

    We haven’t heard back from you in a while, so I’ve gone ahead and marked this thread as resolved.

    Please feel free to open another thread if you’re still having issues with Wordfence.

    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘wp_remote_post() test back to this server failed! Response was: 404 Not Found’ is closed to new replies.