• For some reason, it seems that my “Allow these namespaces” for the REST API isn’t working. There, I have specified:

    oembed
    contact-form-7
    wc
    paypal

    However, when I navigate to: https://adventuretaco.com/wp-json/wc/v1

    It doesn’t return XML; it returns a 403 error page with the content:

    We’re sorry, you are not allowed to proceed
    Your request looks suspiciously similar to automated requests from spam posting software or it has been denied by a security policy configured by the website administrator.

    If you believe you should be able to perform this request, please let us know.

    RID: IXQORVKWH7UNOLEFM35DN4BQ

    • This topic was modified 3 years, 9 months ago by turbodb.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author gioni

    (@gioni)

    It’s working. You need to check the Activity (or Traffic) log to figure out the reason WP Cerber denied the request. Use RID: https://wpcerber.com/rid-request-not-allowed-wordpress/

    Thread Starter turbodb

    (@turbodb)

    Yeah, it seemed to be working on my old site, which is why I was confused – I recently migrated to a new hosting platform.

    Turns out that in doing so, my IP address ended up on the blacklist, because as part of the migration, I was navigating to the default login page (/wp-login) instead of my custom login page.

    Once my IP was blacklisted, I could no longer call the REST API, even though I was a logged in user.

    Strangely, I *was* still able to log into WordPress.

    Now that my IP is no longer blacklisted, things are working as expected. However, it does seem like there is a blacklist/ability to log in/inability to call rest API even when it is enabled for logged in users issue going on here.

    Thanks for the RID pointer – that got me to a point where I could see what was going on. Cheers!

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

The topic ‘REST API exceptions are not respected’ is closed to new replies.