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

Question Request to Confirm Per-Account Process and Security Restrictions in Plesk

Thomas Oryon

Regular Pleskian
Server operating system version
RHEL9
Plesk version and microupdate number
18.0.78
Hello Support Team,

We would like to confirm whether the following restrictions can be applied per customer/subscription in Plesk:

  1. Prohibit the creation of core dumps.
  2. Limit simultaneous processes to a maximum of 5 per account.
  3. Prevent execution of scripts or binaries that may result in a fork bomb.
  4. Restrict customers from running background processes, bots, services, or daemons.
Please confirm whether Plesk provides any built-in option to enforce these controls per customer/subscription.

If these restrictions are not supported directly by Plesk, kindly advise the recommended and supported method to achieve them, such as using systemd/cgroups, custom scripts, OS-level limits, or any other suitable solution.

Awaiting your guidance
 
Back
Top