Access denied with code 403 (phase 4)

Heya

The error message indicates that the issue is related to the ModSecurity Web Application Firewall (WAF) blocking the request due to a rule match.

Disable ModSecurity for your subdomain: disable ModSecurity for your subdomain. This is not recommended for production environments, as it will leave your subdomain more vulnerable to attacks.

Disable the specific rule causing the issue: If you have access to the server configuration, you can disable the specific rule causing the issue (rule 214630). To do this, add the following lines to the Apache configuration file or .htaccess file within your subdomain directory:

<IfModule mod_security2.c>
  SecRuleRemoveById 214630
</IfModule>

After making the change, restart the Apache service:

service apache2 restart

Whitelist your IP address: You can also whitelist your IP address in the ModSecurity configuration to bypass the rule. To do this, add the following lines to the Apache configuration file or .htaccess file within your subdomain directory (replace your_ip_address with your actual IP address):

<IfModule mod_security2.c>
  SecRule REMOTE_ADDR "@ipMatch your_ip_address" "id:1,phase:1,nolog,allow,ctl:ruleEngine=Off"
</IfModule>

After making the change, restart the Apache service.

These options should resolve the 403 error caused by the ModSecurity rule. However, be cautious when disabling security rules or whitelisting IP addresses, as it may expose your subdomain to potential threats. Always ensure that your application is secure and up-to-date to minimize the risk of security vulnerabilities.