• 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.

Plesk Management Service Unstable?

eugenevdm

Regular Pleskian
Plesk Management service giving errors and protected pages aren't protected any more. Below error as per Event Log:

Plesk 8.1 with December 2006 patch.

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 2007/01/15
Time: 01:03:33 AM
User: N/A
Computer: CP2
Description:
Faulting application plesksrv.exe, version 8.100.0.0, faulting module plesksrv.exe, version 8.100.0.0, fault address 0x0007cadb.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 70 6c 65 ure ple
0018: 73 6b 73 72 76 2e 65 78 sksrv.ex
0020: 65 20 38 2e 31 30 30 2e e 8.100.
0028: 30 2e 30 20 69 6e 20 70 0.0 in p
0030: 6c 65 73 6b 73 72 76 2e lesksrv.
0038: 65 78 65 20 38 2e 31 30 exe 8.10
0040: 30 2e 30 2e 30 20 61 74 0.0.0 at
0048: 20 6f 66 66 73 65 74 20 offset
0050: 30 30 30 37 63 61 64 62 0007cadb
 
Hi sshigin,

I think after reboot problem dissappeared... another user suggested reconfigure would have helped - but I didn't do that. I just rebooted and problem appears to have dissapeared thereafter.

regards,
Eugene
 
Back
Top