Recent content by pleskuser67553

Local address, yes, insofar as the senderAddress email domains have a subscription/domain setup on the same Plesk server (each server has a different domain), with DKIM signing enabled using this UI configuration: The only exception is that of the server whose email source output I quoted. It...

Yes, the messages are arriving at the address defined in the Plesk admin profile. However, these messages are not DKIM signed (unlike other admin notifications) so they end up in spam. So I wonder therefore if the alias created by Plesk, described in that support article, is not properly...

@Sebahat.hadzhi Thank you. This resolved my issue of the Anacron errors because there were no more emails from the servers where I applied this workaround. Please can you raise this as a bug?

Relatedly, I'm struggling to understand how these emails are reaching an unrelated external account when they are being sent To: root@server-hostname From: root@server-hostname. I believe I have not set up any forwarding. I'm gratefully informed of the error of course, but consequently they are...

Hi @Sebahat.hadzhi Thank you for your help. I have run those commands. I will wait for the overnight cron to run again.

Hello @Sebahat.hadzhi , here is the readout from one affected server: [root@redacted ~]# ls -la /etc/logrotate.d/ total 96 drwxr-xr-x. 2 root root 4096 Jun 1 12:52 . drwxr-xr-x. 109 root root 8192 May 31 03:48 .. -rw-r--r-- 1 root root 91 Sep 30 2020 bootlog -rw-r--r-- 1 root...

Hello, I've been getting these emails for the past few days from several servers: Subject: Anacron job 'cron.daily' on [hostname redacted] Body: /etc/cron.daily/logrotate: error: imunify-core:22 duplicate log entry for # error: imunify-core:22 duplicate log entry for # error: imunify-core:22...

Thank you @Sebahat.hadzhi. Given that [MDEV-24941] SElinux incorrect label for server socket - Jira says that the bug is fixed and closed, and that one of the fix versions is 10.11.15 (my version since Plesk's auto-update), can I therefore expect the resolution in Plesk's support article to be...

Before applying the workaround I tried MySQL repair in the Diagnose & Repair UI. No issues detected.

Email notification output circa 03:30 UTC System logs when attempting to access a website:

Username: TITLE SELinux is preventing /opt/plesk/php/8.3/sbin/php-fpm from connectto access on the unix_stream_socket /var/lib/mysql/mysql.sock PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE CPU: AMD EPYC-Milan Processor (4 core(s)) Version: Plesk Obsidian v18.0.73_build1800251009.17...

And again @Sebahat.hadzhi after auto-update overnight :( This is embarrassing and no longer funny. CPU: AMD EPYC-Milan Processor (4 core(s)) Version: Plesk Obsidian v18.0.73_build1800251009.17 os_RedHat el9 Operating System: AlmaLinux 9.6 (Sage Margay) Database: MariaDB 10.11.15 PHP 8.3.27 and...

Thank you for this, @Sebahat.hadzhi . Responses indicate all okay. [root@server ~]# apachectl -t Syntax OK [root@server ~]# nginx -t nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful

I will throw my hat in the ring and say that following an auto update on 18 Sept 2025 I got the same error as the original poster @JuanCar Slight differences being, mine was by email notification and noted /etc/nginx/plesk.conf.d/server.conf:14 instead of 15, it happened when updating to...

lol - Google brought me back here again. New installation of AlmaLinux 9.5 New installation of Plesk Obsidian 18.0.67 Update #2 MariaDB updated to 10.11 using the UI updater. Subscription migrated using Plesk Migrator extension. SELinux blocks MySQL socket connection with PHP-FPM 8.4. Above...