403 Access Forbidden Error

  • Resolved gravatard

    (@gravatard)


    2 years, 2 months ago

    Greetings,

    I get the generic error “an error occurred, please try again” after updating from v2.x to v3.0.4.

    All content is gated. No one can access the website. I see your answer to others for this:

    So that error is normally something blocking access to the API, could be a security plugin or something similar. Try clearing any caches.

    I tried clearing all server/website/browser cache but it does not seem to solve the issue.

    I see in console there is an error in file:

    website(dot)com/wp-json/age-gate/v3/check?age_gate…..

    with the status:

    Failed to load resource: the server responded with a status of 403 (Access Forbidden)

    Any chance you can help me troubleshoot? I do use WP Cerber Security plugin, but if that’s blocking it I don’t know where to whitelist Age Gate. =/

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Phil

    (@philsbury)

    Hi @gravatard,

    There’s another thread somewhere with the cerber bit, but here it is:

    WP Cerber -> Dashboard -> Hardening

    Right at the bottom should be a whitelist, just add agegate ad you should be good

    Thanks
    Phil

    Thread Starter gravatard

    (@gravatard)

    I think I figured it out. Here are my troubleshooting steps:

    1. Download and review the .htaccess file. No obvious age gate blocks detected.
    2. Reset file permissions at server level, in case it’s a server block. No change.
    3. Allow “age-gate” REST API namespace in WP Cerber Hardening section. Fixed issue!

    Step 3 seems to have worked. After clearing cache I can access the website using the Age Gate form again without 403 Access Forbidden console error.

    Issue resolved! Thanks!

    Plugin Author Phil

    (@philsbury)

    3 is the way. When checking where the setting was I looked on another site that has an agegate endpoint! age-gate is the right one.

    Have tested the site too and got access.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘403 Access Forbidden Error’ is closed to new replies.