• We actually noticed this issue after running the RankMath SEO Analyzer and testing the HTTP Response Codes of the site with online tools like https://httpstatus.io/ and https://www.webfx.com/tools/http-status-tool/

    Whenever we set the WP Fastest cache to disabled, the tests mentioned above return a 200 and the RM SEO Analyzer works without any issue. The same is true if we clear the cache and run the tests once. After the cache has been created, the tests return 403 again.

    I’ve set the nonce Clear Cache Rule as suggested in other support cases but that did not fix the issue.

    Any recommendations would be appreciated,

    Regards,

    JT

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

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Emre Vona

    (@emrevona)

    could you open your site via a browser?

    Thread Starter jannis01

    (@jannis01)

    Yes, browsing works without an issue when cache is enabled. I can reproduce the same result as the tools mentioned above with:

    curl -s -o /dev/null -I -w “%{http_code}” https://domain/

    Gives back 403 when the cache is enabled and 200 when the cache is disabled. For today I’ll leave the cache enabled till either we can fix this or find a better caching solution.

    Regards, JT

    • This reply was modified 3 years, 4 months ago by jannis01.
    • This reply was modified 3 years, 4 months ago by jannis01.
    Plugin Author Emre Vona

    (@emrevona)

    yes, it returns 403 error but I have no idea about it. First time I see such an issue.

    Thread Starter jannis01

    (@jannis01)

    Indeed weird things happening. I’ve disabled the caching now for you to check again

    Plugin Author Emre Vona

    (@emrevona)

    you should contact your hosting provider. there may be a security protection.

    Thread Starter jannis01

    (@jannis01)

    Ok, will do, thank you very much for your time. We can close this for now.

    Regards, JT

    Plugin Author Emre Vona

    (@emrevona)

    I wish i could have helped you. you are welcome.

    Thread Starter jannis01

    (@jannis01)

    After your hint about security entries, I’ve found the following lines in the .htaccess file that cause the issue.

    # SOFTACULOUS Block .htaccess and .htpasswd
    <Files ~ "^.*\.([Hh][Tt])">
    	Require all denied
    </files>
    # SOFTACULOUS Block .htaccess and .htpasswd End

    Not sure if it’s a good or bad thing to remove those

    Plugin Author Emre Vona

    (@emrevona)

    do not worry about it. you can remove it.

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

The topic ‘403 Error’ is closed to new replies.