Hi @aaron13100
I solved disabling temporarily ModSecurity.
Thank
Aaron (@aaron13100) – I have tested version 2.22.10 with ModSecurity CRS and am no longer seeing a 403 error when saving options on the 404 Solution Options page.
If you get ModSecurity Errors, you can try to disable the rule that causes the error instead of disabling ModSecurity (= firewall) completely.
Different web hosting control panels will have different locations where these settings can be configured.
For Plesk: see https://support.plesk.com/hc/en-us/articles/213378669-A-website-hosted-in-Plesk-fails-to-load-when-ModSecurity-is-enabled-Access-denied-with-code-403
For DirectAdmin: see http://foswiki.org/Support/403-Forbidden-rest-WysiwygPlugin-tml2html
@boossy – Some web hosts do offer that capability, but most web hosts don’t unfortunately. Additionally I have not had much luck in the past with telling users to ask their web host to disable certain ModSecurity rules. I gave up on the futile effort years ago. 😉 If your plugin is not actually doing anything malicious then simply bypass/evade ModSecurity altogether – problem solved.
-
This reply was modified 3 years, 6 months ago by AITpro.