Facebook
TwitterGreeting, i own a plesk admin license and has been ussing it for the last 3-4 years and i love plesk. But in the last 2-3 days i am getting error 403 on my website when i enable Jetpack addon. I tryed multiple thing and nothing work so i have re-installed plesk on a fresh install of debian 11 and did the same thing, once i activated jetpack started to get 403 error again, then i tryed a fresh re-install on ubuntu 22.04 and get the exact same thing. I am out of idea, nothing have change on my plesk config to make this happen and i know how to install and use plesk. Please advise :\
-
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!
-
We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies! -
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.
Issue Plesk + wordpress issue
- Thread starter GhislainR
- Start date
-
- Tags
- please help
403 errors are often linked to ModSecurity rules that kick in on some transactions. Please check your error_log and access_ssl_log files for 403 errors. When you see a ModSecurity entry, carefully examine it for the rule "ID" that is triggered. Then add that ID to the exceptions list in your "Web Application Firewall" dialogue page of the affected subscription.
Similar threads
