Search results

Indeed, by disabling the daily updates of the modsecurity rules, selinux is no longer set to permissive. Is this behavior normal? Is it a generalized bug or does it only affect my server?

I have changed the Atomic Standard rules updates from daily to weekly. If tonight doesn't put selinux on permissive, I could say that the modsecurity rules update leaves selinux on permissive. I will comment tomorrow.

Every night only selinux is changed to permissive. The only recent change I have made on the server, was to change the modsecurity ruleset from comodo to Atomic Standard, because comodo for whatever reason does not install correctly and was giving problems. I have been manually setting selinux...

Every day and at different times I see the following errors in the panel log: I have tried to uninstall and install the add-on, but it still gives the error. Thank you very much for your help

Hello everyone, I am facing a curious problem with my Plesk server that I hope you can help me to solve. When trying to send notification emails from Plesk to the same email address configured for notifications (admin@[CENSORED DOMAIN]), the sending is failing. Here is an extract of the logs I...

I am on almalinux 8.9 [root@mail ~]# systemctl --version systemd 239 (239-78.el8) +PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=legacy No updates are available.

The installed version is grafana 10.1.5. Monitoring works as expected. These warnings only appear when the service is started. I have not modified anything regarding grafana.

Hola recibo estos mensajes en el log del sistema. These messages are repeated from time to time, and when it does, it does so many times. ¿debo preocuparme?, ¿es normal? 2024-01-26 02:33:03 WARNING systemd [1] Daemons del sistema [3] /usr/lib/systemd/system/grafana-server.service:35...

I am receiving these alerts in mariadb ******** mariadbd[418459]: 2024-01-19 12:06:57 2126 [Warning] Aborted connection 2126 to db: 'psa' user: 'admin' host: 'localhost' (Got an error reading communication packets) ******** mariadbd[418459]: 2024-01-19 14:06:53 8101 [Warning] Aborted connection...

Thank you very much @Peter Debik, I managed to solve it following the indications in this article: https://support.plesk.com/hc/en-us/articles/12377928655767-MySQL-MariaDB-fails-to-start-on-a-Plesk-for-Linux-server-Can-t-open-and-lock-privilege-tables

I have managed to keep the server running by booting Mariadb in safe mode, but it won't boot in normal mode. This has been when updating plesk. Mariadb version 10.11.6

I already voted for it, but waiting to fix something so important, that most plesk users probably don't even know it exists, and the day they find out it's because it has caused them problems, is absurd. This should not be considered a new feature, but a bug, which should be fixed.

Messages sent from MAILER-DAEMON go to the spam folder. This is a problem, because if a user for example of gmail, sends several mails to our mailboxes and requests delivery confirmation, mailer-deamon sends the confirmation message and this does not approve dmarc, it fails both spf and dkim...

In almalinux 8.9 just installed, without admin user change, the same problem.

yes, I'm getting it too. Almalinux 9.3

Unfortunately since the new update I have not been able to get docker running on plesk. I thought it was intentional. Luckily I had a backup of the docker extension and only with this one it still works. I installed it manually, and disabled automatic updates so it won't update because it...

Since the last update that allows changing the admin user name, the app has stopped working correctly. The lower buttons of the app are no longer visible. Reset the username to admin, it shows them again, but gives credentials error.

I can confirm that plesk and almalinux 9.3 also throw constant selinux warning messages. Something is not working as it should. tested on a completely clean install.

I have reinstalled the server since I have not deployed it yet, installing almalinux 9 and plesk, and I have restored a plesk backup. And in the system log I constantly get the following message: SELinux is preventing /opt/plesk/php/8.1/sbin/php-fpm from read access on the file shadow. *****...

In case someone has the same problem. Plesk and cockpit are incompatible. To install plesk and not have problems, it is necessary to install Plesk over the minimum installation of Almalinux 9.