Post comments 403 Error, malformed Query String

[AITpro Admin]

@ keewee – BPS has a feature called Custom Code.  It is located here > BPS Pro > htaccess File Options > Custom Code tab > Root htaccess File Custom Code accordion tab.  Check this Root htaccess Custom Code text box:  1. CUSTOM CODE TOP PHP/PHP.INI HANDLER/CACHE CODE and remove/delete all htaccess code except for your LiteSpeed Cache htaccess code.

Any htaccess code saved in Custom Code is written to your active root htaccess file.  So you need to delete the duplicate htaccess code that is saved in Custom Code, save your changes and activate Root folder BulletProof Mode.

[keewee]

never mind last question on this page. The outdated rules. Can you please help me with the skip/bypass rule or whatever else is needed for the error listed below? Been looking for hours, this error has come up as unchanged error many times. And this same error is happening on other sites with same hosting account?

[403 POST Request: May 8, 2022 - 10:17 pm]
BPS Pro: 16.6
WP: 5.9.3
Event Code: WPADMIN-SBR
Solution: https://forum.ait-pro.com/forums/topic/security-log-event-codes/
REMOTE_ADDR: GDPR Compliance On
Host Name: 45.32.210.159.vultrusercontent.com
SERVER_PROTOCOL: HTTP/1.1
HTTP_CLIENT_IP: GDPR Compliance On
HTTP_FORWARDED: GDPR Compliance On
HTTP_X_FORWARDED_FOR: GDPR Compliance On
HTTP_X_CLUSTER_CLIENT_IP: GDPR Compliance On
REQUEST_METHOD: POST
HTTP_REFERER: https://mysite.com/wp-admin/post.php?post=199&action=edit
REQUEST_URI: /wp-json/wp/v2/pages/199?_locale=user
QUERY_STRING: _locale=user

[AITpro Admin]

Edit|Update:  keewee’s issue has been confirmed as one of the known numerous problems caused by ModSecurity CRS.

@ keewee – There is no default BPS root or wp-admin htaccess code that would block that POST Request.  Do troubleshooting steps #1 and #2 here > https://forum.ait-pro.com/forums/topic/read-me-first-pro/#bps-pro-general-troubleshooting. Then check all custom htaccess code that you have added to either the root or wp-admin htaccess file to see if your custom htaccess code is causing the block. It is also possible that ModSecurity installed on your host server is causing this block.  BPS logs all 403 errors whether or not BPS is causing a 403 error.

[Author]

Posts