• 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 Panel 11 for Linux (CentOS 6) & SELinux

PriyanA

Regular Pleskian
Hi,

I'd like to use SELinux on my VPS (Plesk Panel 11, CentOS 6, Newly Built) as a extra security feature.

Came across many posting that Plesk NOT recommending to use SELinux "Enforcing"

Have anyone successfully done this?

Please post your ideas.
 
PriyanA, there's no sense in blaming SELinux unless you post your relevant audit log file entries and 'plesk' SELinux module version. List of enabled and disabled SELinux booleans may also help track down the issue.

While it's true that there are problems with SELinux support on Plesk servers here and there, clean installation of Plesk should behave well. You may also want to run restorecon on any offending files seen in audit log first.
 
Okay, looks like some kind of trouble with SELinux booleans used by Plesk.

Try:
# getsebool -a | grep httpd_can_bind_all_ports

If it shows that it's off, then try to re-enable nginx as a reverse proxy server:
# /usr/local/psa/admin/bin/nginxmng -d
# /usr/local/psa/admin/bin/nginxmng -e

If there is no output at all (edit: from the getsebool command above), then this most probably means that you have wrong 'plesk' SELinux module version (or none at all), hence in much more trouble than only httpd start problems.

Hope this helps.
 
Glad I could be of assistance.

So your problem is solved? Did you install appropriate version of 'plesk' SELinux module then?
 
Unfortunately, you will have countless problems unless you install proper policy module.

To find out which version of Plesk policy module is installed:
# semodule -l | grep plesk

To manually (re)install current version of Plesk policy:
# semodule -s targeted -i /usr/local/psa/etc/plesk.pp
or maybe without "-s targeted" or with other store depending on your system.

But I recommend just running /usr/local/psa/etc/selinux_policy_upgrade_trigger instead.
 
Nikolay. thank you very much for your support.

Ive seems overcome all the problems and plesk+domains are working fine. i'll post the full steps once my VPS is re-built. hoping it will help someone looking for additional security.
 
Back
Top