• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question WordPress plugin access rule error

Chad

Basic Pleskian
Hello,

Installed a recent plug-in for WordPress and now see this following error.

- *660475 access forbidden by rule

All previous plug-ins are working correctly and logs are clean, installed this one and now see this error and the plug-in is not loading correctly.

Have looked around to find out what this rule could be, no luck and was wondering if anyone here may have any insight as to what causes this type of error in Plesk Onyx.

Thank you,
 
What makes you think that a control panel and server management software is responsible for a faulty Wordpress plugin? You are saying that all your other plugins work correctly, and there are hundreds of thousands of Wordpress websites that run trouble-free in the Plesk environment.
 
Hi Peter,

Don't take this as I'm blaming Plesk - in no way is that the case. Just looking for insight as to what this rule could be relating too - whether it's a rule within Plesk that is not allowing or possibly more of a permissions error. Within the plug-in details the error it's seeing mentions permissions, usually permissions show a similar error within Plesk logs, so just not sure what this rule is referencing.

Any thoughts or ideas?
 
Back
Top