Resolved Some WordPress plugins got 403 errors

[bmalkoc]

Hello. I did fresh install Plesk Obsidian Web Admin Se Edition Version 18.0.42 Update #1 But some plugins got 403 forbidden errors.

Plesk: Obsidian Web Admin Se Edition Version 18.0.42 Update #1
Server: Nginx
PHP: 8.1.4 Fpm App. by nginx.

Here is Rank Math Pro error:


Here is Elementor Pro error:


I also tried, Proxy mode, Php 7.4 Fpm and Fastcgi. I don't know what can i do more to fix this problems.

 

[Bitpalast]

Solution:
Check your error_log (icon ("logs")) for ModSecurity errors and code 403. In the error description you will find a ModSecurity rule ID. Add the ID to the "Web Application Firewall" rule exclusions list. There could be more than one ID. Add them all.

 

[bmalkoc]

Hello @Peter Debik Thank you for you advice. But i disabled ModSecurity (Web App. Firewall) for this domain. And there is no error log for ModSecurity.

 

[bmalkoc]

And got this errors also in the Site Health Checker

 

[Bitpalast]

And what are the details for the 403 error in your error_log?

 

[bmalkoc]

@Peter Debik
Here is some errors from log:

 

[Bitpalast]

"no such file or directory" --> The physical location does not exist and an .htaccess rule is missing to simulate the path or a rule exists but is not used because Nginx-only hosting is used.

 

[bmalkoc]

@Peter Debik ok. Can you advice any solution?

Here is similar logs:

 

[Bitpalast]

Maybe you should first check whether the files and directories exist physically on the server?
If these exist, do they have correct permissions and owners so that the web server can access them? E.g. group read/write permissions?
Then you could check if .htaccess rules are needed to operate your widget and if these have been implemented.
Then you could check whether you are using Apache PHP and Apache hosting ("proxy mode" in Nginx/Apache webhosting settings). If not, activate it, because else .htaccess won't take effect.

 

[bmalkoc]

This files are not physical. It is rest-api url. I think it not related to Plesk (maybe). I will try other solutions. Thank you so much. @Peter Debik

 

[GregoryChang]

Maybe you should first check whether the files and directories exist physically on the server?
If these exist, do they have correct permissions and owners so that the web server can access them? E.g. group read/write permissions?
Then you could check if .htaccess rules are needed to operate your widget and if these have been implemented.
Then you could check whether you are using Apache PHP and Apache hosting ("proxy mode" in Nginx/Apache webhosting settings). If not, activate it, because else .htaccess won't take effect.

I don't think it has anything to do with Plesk.

 

[bmalkoc]

I fixed with this nginx custom config.

if (!-e $request_filename){
    rewrite ^(.*)$ /index.php break;
}