Unclear Block Reason for HTTP 503 Error

  • Resolved jhanby

    (@jhanby)


    5 years, 2 months ago

    My site has been intermittently encountering the error in the linked screenshot, and I’m not clear what blocking rule is being triggered. Rate limiting is disabled and we turned off participation in the Wordfence Security Network because it was triggering too many 503 errors for our visitors as well.

    Which brings me to my next theory. We’re currently hosting it on Liquid Web Cloud Sites, and we’re using the X-Forwarded-For HTTP header method for determining IP address. This has 2 IP addresses listed in the plugin settings, one of which I believe is the Cloud Sites load balancer in addition to mine client IP address. I’m wondering if this is normal behavior, having 2 IP addresses, and if not, could it explain why the 503 error is happening (because perhaps all requests have the same common IP addresses coming from Liquid Web alongside the true client IP, and the blocking rules are being triggered for some visitors incorrectly based on those common IPs.

    Ideas welcome!

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

Viewing 6 replies - 1 through 6 (of 6 total)
  • MissTT

    (@misstt)

    5 years, 2 months ago

    I am having the same issue with users not being able to log in as seeing ‘Your access to this site has been temporarily limited by the site owner. Please try again in a few minutes (HTTP response code 503).

    Can’t get to the bottom of what is causing it – any advice on what to do would be appreciated.

    Thanks in advance!

    Plugin Support WFAdam

    (@wfadam)

    5 years, 2 months ago

    Hello @jhanby 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.

    It sounds like the IP detection might be misconfigured. The diagnostic will let me know exactly what is happening.

    Sorry @misstt but as per forum guidelines below, could you please open your own topic and we would be glad to assist you:
    “Unless users have the exact same version of WordPress on the same physical server hosted by the same hosts with the same plugins, theme, and configurations, then the odds are the solution for one user will not be the same for another. For this reason, we recommend people start their own topics.”

    Thanks again!

    Thread Starter jhanby

    (@jhanby)

    5 years, 2 months ago

    Thanks @wfadam! Just sent it. Also, I received the 503 error for the first time myself, but was able to send the unlock email to myself and successfully regained access to the site that way. The IP address referenced in the email IS an IP used by Cloud Sites, not my client IP, even though that should be also referenced in the diagnostic report. Let me know if you want me to forward that unlock email for any reason. Looking forward to hearing your thoughts.

    Plugin Support WFAdam

    (@wfadam)

    5 years, 2 months ago

    Thanks for sending that diagnostic!

    This is a common issue with LiquidWeb as they proxy their traffic through a few IPs. I noticed you have a few trusted proxies set up in Wordfence > All Options > General Wordfence Options but we will need to add the following as well.

    207.246.240.0/24
    207.246.240.102

    This should correct the issue of your site not being able to identify the correct IP from the traffic. Currently, it is thinking everyone has the same IP so any Brute Force blocks are causing everything to be blocked.

    Let me know if this helps!

    Thanks again!

    Thread Starter jhanby

    (@jhanby)

    5 years, 2 months ago

    Perfect! That’s what I thought was going on, but thanks for letting me know which ones I didn’t have accounted for in the trusted proxy list. Thanks @wfadam !!

    Plugin Support WFAdam

    (@wfadam)

    5 years, 2 months ago

    Great! As long as everything works! IP detection can cause so many issues and can be frustrating!

    Let me know if you need anything else!

    Thanks again!

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Unclear Block Reason for HTTP 503 Error’ is closed to new replies.