• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue SELinux Access Control Errors

Greg Sevastos

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.
 
You must log in or register to reply here.

Similar threads

G
Question Does Plesk on Ubuntu 22.04 support SELinux?
Replies
2
Views
1K
Maarten
M
C
Question Monitoring a Plesk Server (services, domains, etc.) with Zabbix
Replies
1
Views
478
scsa20
scsa20
H
Question SSH user can see other subdomain directories even with chrooted shell?
Replies
3
Views
388
Raul A.
R
F
Question Plesk Migrator Error: Access denied for user 'admin'@'127.0.0.1' (using password: YES)"
Replies
7
Views
20K
Sebahat.hadzhi
Sebahat.hadzhi
B
Issue High latency, unreliable performance & 522 errors on a Plesk server that ran fine for 6+ months
Replies
8
Views
1K
HHawk
HHawk
Back
Top