Recent content by mizar

Hi! This error can be caused non-update extensions. May be you have customer extension catalog configured by catalog.url in /usr/local/psa/admin/conf/panel.ini ? If yes, temporary comment the line and run plesk daily UpgradeExtensions. If no, try to compare installed version with version from...

Hi, Should be resolved. Let me know if the problem persists

> Presumably, the weak algorithm issues will still be resolved as part of the 18.0.69 release, as per this previous Plesk post ? Yes, Plesk 18.0.69 will be signed with new GPG key. Please, check the release notes for the details

Hi! We are updating GPG key for signing the repositories to stronger one. As you are on 18.0.68, you need to apply Plesk update using `plesk installer update` command or using UI to import the new GPG key

Hello! Looks good. Unfortunately, I'm out of ideas what else can be wrong. Could you please send me output of strace -f -v -s400 /usr/local/psa/admin/sbin/osdetect 2>&1 in PM? Or, if you have a contract with support, create a support ticket?

Hello! Very strange. Is any chance that /etc/redhat-release is modified? Plesk reads exactly first line from it. What rpm -V centos-release shows?

Hello! osdetect tries to check following files /etc/debian_version, /etc/CloudLinux-release, /etc/vzlinux-release, /etc/almalinux-release, /etc/rocky-release. If one of these files exists and has empty first line, osdetect can fail with such error. Could you please check your server?

Hello! You might want to also consider recidive jail. It is analyse fail2ban log, and if some ip is banned several times (5 by default), it will be banned for a long time (1 week)

Hello, /etc/redhat-release is used to detect CentOS 7 Thanks,

Hello, Yes, "Run now" not via cron, because cron doesn't have mechanism to run job once.

Hello! Plesk 18.0.47 is very outdated and it was removed from download site, so that's why you cannot manage components. You can either remove unneeded packages via yum (less desired), or first update to latest version (18.0.64 at the time of writing), and then manage components via Plesk installer

Hello! Could you clarify what is the problem? `usermng --isquotable` returns 0, that means that quota is supported

It's applicable for any OS. And "Allow users to use sendmail" flag is unrelated to chroot and mostly intended to forbid sending emails via system users. Packing any SMTP client (mini_sendmail, msmtp or else) as /usr/bin/sendmail with appropriate configuration will do the work.

But clean Plesk installation doesn't have a sendmail in the chroot and mail or sendmail commands doesn't work (and never works) in the chroot out of the box. I can only guess that previously your cron job works with non-chrooted shell.

Hello! I doubt that it's enough to add /usr/sbin/sendmail to the chroot to make it send the emails - because postfix sendmail need to write file to the postfix queue, which is out of the chroot, and cannot be easily added. May be emails was send via SMTP or by cron itself?