Did wordfence.com block all the non-ISP ASN?

  • Resolved sao987

    (@sao987)


    3 months, 3 weeks ago

    Hi,

    Firstly, my WordPress website has no problem using Wordfence, so it’s not related to the actual product.

    However, my company uses the Ucloud dedicated network in our office, and it’s not possible to access the wordfence.com website because I get this error.

    403 ERROR The request could not be satisfied. Request blocked. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
    If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
    Generated by cloudfront (CloudFront) Request ID: --REDACTED--

    It appears that CloudFront CDN blocked all these access attempts. I tested servers on the Oracle network and the Alibaba Cloud network, but all were blocked by AWS CloudFront with a 403 error when trying to visit wordfence.com.

    Isn’t this way too restrictive? Only home ISPs are allowed to visit wordfence.com now?

    Thanks

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

  • We have the same issue – all of a sudden we’re getting blocked when using the Vulnerability Feed API:

    https://www.wordfence.com/api/intelligence/v2/vulnerabilities/production

    [2024-08-05 07:06:39] API HTTP response code: 403

    And curl request from the service to wordfence.com is 403 by CloudFront.

    curl -IL wordfence.com

    HTTP/2 403
    server: CloudFront
    date: Mon, 05 Aug 2024 08:37:45 GMT
    content-type: text/html
    content-length: 919
    x-cache: Error from cloudfront

    It’s fine when doing so using local ISP.

    Plugin Support wfpeter

    (@wfpeter)

    Hi @sao987,

    We experienced an outage over the weekend which caused some issues with connectivity. This morning, we noticed that some of our recovery measures may have been causing ongoing connectivity issues for certain customers. We’ve since implemented a fix that should allow affected customers to connect to Central and other services.

    Note: @fixednet I had seen your message related to Wordfence Intelligence API before consulting the team about the 403s seen on a wider level. Looking now, it’s likely you were affected by the same situation, so my apologies for not spotting that but for future issues with that product, contacting the email address I provided is still the best route to take.

    Many thanks,
    Peter.

    Thread Starter sao987

    (@sao987)

    I can confirm the block is now fixed. Thanks

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.