• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue IIS/ASP.NET/Umbraco exception on on w3wp.exe and pcre.dll

Aapklub

New Pleskian
I have a Windows Server 2025 VPS managed using Plesk for Windows. On it, I host multiple Umbraco Websites. Since recently, an issue occurs where some sites' application pools appear to crash, taking that specific whole site offline until they are recycled. I can consistently reproduce it by attempting to sign in to the Umbraco backoffice on a site. In (Chromium) browsers, this yields ERR_HTTP2_PROTOCOL_ERROR. The website/Umbraco logs don't show any peculiarity, while the logs in the Windows Event viewer display following error:

Code:
Faulting application name: w3wp.exe, version: 10.0.26100.1882, time stamp: 0xc6bd45bd
Faulting module name: pcre.dll, version: 0.0.0.0, time stamp: 0x63b62f6d
Exception code: 0xc00000fd
Fault offset: 0x0000000000013ecf
Faulting process id: 0x1F24
Faulting application start time: 0x1DBEAD3ACB044B9
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\WINDOWS\System32\inetsrv\pcre.dll
Report Id: 05530de0-f951-4855-b3e0-b1ece5a4a8fd
Faulting package full name:
Faulting package-relative application ID:


The faulting module appears to be an IIS DLL, which makes sense, as multiple sites display this behaviour, although nothing has changed on the system recently to warrant this.
 
Back
Top