• 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 error is thrown for DELETE/ PUT requests

Fit

New Pleskian
Server operating system version
Windows Server 2019 10.0.17763 Build 17763
Plesk version and microupdate number
18.0.60 #1
When a DELETE or PUT request is sent, a 403 error is thrown. Per another thread, the solution was to check for a rule ID in the error but a rule ID is not displayed in the error. The error is listed below.

<?xml version="1.0" encoding="UTF-8" ?>

<?xml-stylesheet type='text/xsl' href='freb.xsl'?>

<!-- saved from url=(0014)about:internet -->

<failedRequest url="https://friendly-blackwell.[server IP].plesk.page:443/api/Customer/DeleteRequest/e88e5cbd-393b-48b0-8fc2-b8f9ef5e55ab"

siteId="8"

appPoolId="friendly-blackwell.[server IP0].plesk.page(domain)(4.0)(pool)"

processId="14844"

verb="DELETE"

authenticationType="NOT_AVAILABLE" activityId="{80000317-0000-F600-B63F-84710C7967BB}"

failureReason="STATUS_CODE"

statusCode="403"

triggerStatusCode="403"

timeTaken="0"

xmlns:freb="http://schemas.microsoft.com/win/2006/06/iis/freb"

>

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="WWW Server" Guid="{3A2A4E84-4C21-4981-AE10-3FDA0D9B0F83}"/>

<EventID>0</EventID>

<Version>1</Version>

<Level>0</Level>

<Opcode>1</Opcode>

<Keywords>0x0</Keywords>

<TimeCreated SystemTime="2024-05-02T12:06:23.674Z"/>

<Correlation ActivityID="{80000317-0000-F600-B63F-84710C7967BB}"/>

<Execution ProcessID="14844" ThreadID="7324"/>

<Computer>[server IP]</Computer>

</System>
 
Thank you for providing the support article! After trying the first two solutions, the last one, adjusting the ModSecurity, worked. Thank you again!
 
Back
Top