Wordfence – QUIC.cloud CDN

  • Resolved gatsman

    (@gatsman)


    3 months, 2 weeks ago

    Hello i think after the latest update it is blocking QUIC.cloud
    In the LiteSpeed Cache General Settings – Domain Key i get:

    Notice:
    There was a problem with retrieving your Domain Key. Please click the Waiting for Refresh button to retry.
    There are two reasons why we might not be able to communicate with your domain:
    1) The POST callback to https://www.**********.com/wp-json/litespeed/v1/token failed.
    2) Our Current Online Server IPs was not allowlisted.
    Please verify that your other plugins are not blocking REST API calls, allowlist our server IPs, or contact your server admin for assistance.:
    See image: https://ibb.co/c2VxyZL

    I tried to add all the IP’s in Wordfence – Advanced Firewall Options – Allowlisted IP addresses that bypass all rules like LiteSpeed suggests but with no luck
    “Before generating key, please verify all IPs on this list are allowlisted: Current Online Server IPs“

    *If i deactivate Wordfence it will pass but don’t know if it will have any affect when i reactivate Wordfence

    • This topic was modified 3 months, 2 weeks ago by gatsman.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @gatsman,

    There are a few factors with QUIC.cloud where the Trusted Proxy Preset for it should be picked in Wordfence > All Options > General Wordfence Options > How does Wordfence get IPs > +Edit Trusted Proxies. Some customers also had success using X-Real-IP to obtain user IPs for their visitors, although I’ve generally seen the recommendation that X-Forwarded-For is the one that should be used.

    Having said all that, I wouldn’t expect a previously working site (especially if the above is all configured correctly) to break during a plugin update. If IP detection and proxies aren’t the problem, I would hit the “Waiting for refresh” button, then check in Wordfence’s Live Traffic for a recent block. Check the block reason after clicking the block itself, or eye icon in the corner, to expand it. You may be able to allowlist directly from here to make sure your https://www.**.com/wp-json/litespeed/v1/token path can be reached.

    Let us know how you get on,
    Peter.

    Thread Starter gatsman

    (@gatsman)

    I was able to make it work
    Thank you

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