• Resolved michalcz

    (@michalcz)


    Hello, i have problem with scan, scan does not start with this error msg:

    wp_remote_post() test back to this server failed! Response was: 401 Unauthorized
    This additional info may help you diagnose the issue. The response headers we received were:
    HTTP/1.0 401 Unauthorized
    Cache-Control: no-cache
    Connection: close
    Content-Type: text/html
    WWW-Authenticate: Basic realm="wp"
    
    <html><body><h1>401 Unauthorized</h1>
    You need a valid user and password to access this content.
    </body></html>

    Whole site (domain) is password protected with user and password on nginx configuration.
    How to make test running, can i add some login details to WF options? please where?
    Or i need to ask server admin to exclude wordfence servers IP from pass protecting in nginx config? and what is the ips of WF servers.
    I cant find similar issue with pass protected site in documentation.
    Web domain(url) is private for internal use only, so i cant write website url there.

    Thanks for your help.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • WFGerroald

    (@wfgerald)

    Hey @michalcz,

    Our servers are from 69.46.36.0 to 69.46.36.32. Can you please whitelist this range and let me know if it helps? Note that Wordfence will need access to the wp-admin > admin-ajax.php. If it’s blocked, Wordfence will not be able to scan, along with the possibility of breaking other plugins and WordPress functionality.

    https://www.wordfence.com/help/scan/troubleshooting/#if-your-scans-arent-starting

    Please let me know how it goes.

    Thanks,

    Gerroald

    Hey @michalcz,

    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,

    Gerroald

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