• 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 Is it safe to use Memcached in a shared Plesk hosting environment?

ranjithkr

New Pleskian
Server operating system version
CentOS Linux release 7.9.2009 (Core)
Plesk version and microupdate number
Plesk Obsidian 18.0
Is it safe to use memcached in a shared plesk hosting environment ?
It is not safe when using a single daemon (as described in the article you linked to). There is no way to isolate data in memcache and there is noway to authenticate to memcached unless running multiple daemon on different ports.
 
But is it practical to run multiple daemons on different ports in a shared plesk environment with more than 100+web applications ? Is there any alternative solutions ?
 
Back
Top