• 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 SELinux Access Control Errors

Greg Sevastos

New Pleskian
Server operating system version
Almalinux 9.5
Plesk version and microupdate number
18.0.66 #1
Hi,

I have a fresh install of Almalinux 9.5 + latest Plesk installed with Imunify360.

I’m seeing control errors like the following in SELinux via cockpit:

SELinux is preventing /opt/plesk/php/8.2/sbin/php-fpm from write access on the sock_file /opt/imunify360/lib/proactive.sock

Shouldn’t Plesk have built in rules to handle communication with Imunify for SELinux?

If not, I’m assuming allowing access is completely fine here?

Looking forward to any input.

Cheers
 
Hi scsa20,

The imunify360 install instructions below were carried out before this started to show up:

checkmodule -M -m -o /var/imunify360/imunify360.mod /opt/imunify360/venv/share/imunify360/imunify360.te
semodule_package -o /var/imunify360/imunify360.pp -m /var/imunify360/imunify360.mod
semodule -i /var/imunify360/imunify360.pp

Not sure if I need to apply them again.
 
Back
Top