Facebook
Twitter-
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.
Resolved 403 - Forbidden: Access is denied for PUT and PATCH Request
- Thread starter AV0408
- Start date
-
- Tags
- .net core 7 web api
hitesh-wappnet
New Pleskian
I got the similar issue in my Nest JS API. PUT,PATCH,DELETE methods gives 403 - Forbidden error.
Solution :
Go to Plesk -> 'Tools & Settings' -> Web Application Firewall (ModSecurity) -> Settings
- Rule set : Atomic Standard
This worked for me.
Solution :
Go to Plesk -> 'Tools & Settings' -> Web Application Firewall (ModSecurity) -> Settings
- Rule set : Atomic Standard
This worked for me.
Switching the ruleset might not be necessary. For one case, another ruleset might work, but it may create false positives in other cases.
Instead, examine the error_log entry where the 403 error is logged. It will mention an [ID .......] field. This is the rule ID that triggered the 403 block. You could at it as an exception to the rule exceptions in the "Web Application Firewall" dialog page.
Instead, examine the error_log entry where the 403 error is logged. It will mention an [ID .......] field. This is the rule ID that triggered the 403 block. You could at it as an exception to the rule exceptions in the "Web Application Firewall" dialog page.
hitesh-wappnet
New Pleskian
Okay, I have again enabled Rule set : OWASP . In my case, I have deactivated 'OWASP_CRS' Rule and everything is working as expected.
Thank you for the correct solution.
Thank you for the correct solution.
