Osm Jili Gcash Register.REGISTER NOW GET FREE 888 PESOS REWARDS!

Resolved radioparanormalium
(@radioparanormalium)

10 months, 2 weeks ago

There seems to be an issue with version 8.5.1. After upgrading WooCommerce last night I started getting 403 errors when I tried to load my website. First page loaded partially, at fome point I noticed images aren’t loading anymore, and when I hit F5 I got an ‘access denied’.

After doing some research I realized the issue is gone when I open my page in Incognito mode. But then, again, first load ALMOST ok, refresh – and I get 403.

Apparently the plugin messes something up with cookies because I found that clearing them makes me able to load my page normally again.

After clearing cookies I can go directly to WordPress’s Dashboard and everything works fine until I go back to home page where another 403 just waits to make me have a heart attack. ??

After I rolled WooCommerce back to 8.4.0 the issue seems to be gone.

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

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

Rok Megli?
(@rokmeglic)

10 months, 2 weeks ago

Please check this WooCommerce 8.5.1 issues with Web Application Firewall?(ModSecurity)? — Develop with Woo.

banacan99
(@banacan99)

10 months, 2 weeks ago

@rokmeglic

Thank you for sharing that link. I was able to follow the instructions there and turn off the Order Attribution feature (which I don’t need) and now my site is working properly again.

You saved me the last of my hair! Thanks.
Plugin Support Sandip Mondal – a11n
(@sandipmondal)

10 months, 2 weeks ago
Hi folks,

Sorry to hear that the plugin updated caused an issue.

This issue has been reported here and our developers are aware about it:
- https://github.com/woocommerce/woocommerce/issues/43681
This problem is related to a new feature available since WooCommerce 8.5 called Order Attribution Tracking

There are two ways that one can go about the 403 errors:
1. In case you do not want to use this feature you can disable it. Info from FAQ Cookies are blocked by a Web Application Firewall (WAF)
2. In case you want to use it then a specific WAF rule triggering the issue needs to be updated or disabled to allow proper functioning of the sites and the feature. For example, the following Plesk article explains how to do it:?Plesk WP website is not accessible with the 403 Forbidden error after a WooCommerce plugin update. You can also reach out to your assist you with this.
Also, thank you @rokmeglic for sharing that announcement link!

I hope this information helps.

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

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