Support » Plugin: Wordfence Security - Firewall & Malware Scan » Scans being Blocked even though scan IP is defined in htaccess

  • Resolved davbot

    (@davbot)


    Hello,

    Having a bit of an issue here.

    we have a site where we have had to put an htaccess into the wp-admin directory, only allowing certain IP’s dashboard access. I have added the IP’s listed in the help page:
    69.46.36.0 to 69.46.36.32. (33 IPs total)

    and in the diagnostics section I still get:
    wp_remote_post() test back to this server failed! Response was: 403 Forbidden
    This additional info may help you diagnose the issue. The response headers we received were:
    HTTP/1.1 403 Forbidden
    Server: nginx/1.19.3
    Date: Wed, 28 Oct 2020 18:36:15 GMT
    Content-Type: text/html; charset=iso-8859-1
    Transfer-Encoding: chunked
    Connection: close
    Vary: Accept-Encoding
    Content-Encoding: br

    <html><head><title>Error 403 – Forbidden</title><head><body><h1>Error 403 – Forbidden</h1><p>You don’t have permission to access the requested resource…..

    Is the help docs missing IP’s to allow via htaccess?

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

    (@wfadam)

    Hello @davbot and thanks for reaching out to us!

    Can you send a diagnostic report to wftest @ wordfence . com? You can find the link to do so at the top of the Wordfence Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    Usually, when the remote post is showing a 403, it’s because when the site sends out the signal to our scan server, and the signal comes back, it’s being blocked. The biggest reason I see this is because the admin-ajax.php is blocked.

    Thanks!

Viewing 1 replies (of 1 total)
  • The topic ‘Scans being Blocked even though scan IP is defined in htaccess’ is closed to new replies.