Scan Failed (503)

  • Resolved Jim

    (@releasejim)


    5 years, 1 month ago

    WordFence scan cannot be started:

    wp_remote_post() test back to this server failed! Response was: 503 Service Unavailable
    This additional info may help you diagnose the issue. The response headers we received were:

Viewing 3 replies - 16 through 18 (of 18 total)
1 2
  • Plugin Support wfpeter

    (@wfpeter)

    5 years ago

    @sallyruchman, thank-you for informing us of the steps you took to get the scans running, I will inform the wider team and update our knowledge base documentation on dealing with this feature in future. However, the 69.46.36.0/27 range is an old range used before a server migration performed a number of months ago, so there is now a new series of IPs that should be allowed in Cloudflare – but you’ll be pleased to know it’s a lesser quantity.

    I would you recommend both yourself and @releasejim allowing all 6 IPs seen on: https://www.wordfence.com/help/advanced/#servers-and-ip-range

    Let me know how that goes for you.

    Peter.

    sally

    (@sallyruchman)

    5 years ago

    @releasejim happy to hear that the scans now work for you as well

    @wfpeter thanks for the information regarding IP ranges. I allowed just the six recommended now, removed the 69.46.36.0/27 range from CF, and can confirm that the scans still work with Bot fight mode enabled 🙂

    br
    Sally

    Plugin Support wfpeter

    (@wfpeter)

    5 years ago

    @sallyruchman That’s great, thank-you for your feedback and keeping us up-to-date.

    If you have any further Wordfence questions in future, please don’t hesitate to start a new topic and we’ll always be glad to help out.

    Peter.

Viewing 3 replies - 16 through 18 (of 18 total)
1 2

The topic ‘Scan Failed (503)’ is closed to new replies.

  • 18 replies
  • 3 participants
  • Last reply from: wfpeter
  • Last activity: 5 years ago
  • Status: resolved