Recent content by Bitpalast

Backups cannot be written to an external FTP repository directly. Some sort of temporary files are required. They are stored in the path DUMP_TMP_D defined in /etc/psa/psa.conf. Also, a local copy of the data that needs to be packed and uploaded plus a few XML data files on the backup of the...

Note here, trying since noon. Neither plesk installer --select-release-current --upgrade-installed-components offers a download, nor has the FAQ article been updated that a patch has actually been published. What am I missing? 18.0.77 #2 on Alma

Comodo (free) running on Apache (ModSecurity 2.9)

Where did you add your lines?

It requires an Apache reload after the change, but it works. Thank you. I think @Azurel has a point. This should be checked.

@Sebahat.hadzhi After installation of GoAccess on a Plesk default installation we also see the 500 internal error page when opening /plesk-stat statistics. I had to add <IfModule mod_security2.c> SecResponseBodyLimit 268435456 </IfModule> to the Apache directives of the subscription to...

Thank you for this advice. It does work with dnf update --disablerepo='*' --enablerepo='imunify360-rollout*' rustbolit but it also requires to update the PUM list manually afterwards as Plesk still seems to think i needs to update the (older) rustbolit file. We'll just do it for all servers...

I should add that the issue prevents other updates in the same queue to complete, because PUM stops the update process when one of the items in the queue cannot be downloaded in full.

Since a while, at least a month, we are experiencing frequent issues with upgrades of ImunifyAV components. a) Some files are not downloading properly. Sometimes these files sit in the update queue for for days or longer. 2026-05-13 08:39:45 INFO: Downloading...

For the Plesk internal PHP use, does Plesk use the PHP settings installed in the /opt/plesk/php/<version>/etc/ paths for any of their features?

That's partly right. The page still talks about the test repo, but see the solution on disabling the module by creating a .conf file in the description. This will do (unless these modules are not modules, but built into the kernel, which however will be extremely rare for this). So what you want...

The on-the-fly solution shown in Dirty Frag (CVE-2026-43284, CVE-2026-43500) vulnerability fix is ready for testing is sufficient for it. No reboot required (at least not now). Not linked to the Apache issue discussed in this thread, though.

Thanks a lot for bringing this up. Nevertheless, I suggest opening a new topic for this and similar entries.

While this short input explains removal issues with a database previously used with Joomla, similar issues might appear with other former APS applications that can no longer be removed through the APS catalog, because the feature was completely removed. Hence it appears that such databases can...

Regarding the latest disastrous Linux vulnerability, CVE-2026-31431, multiple sources recommend mitigating the issue by disabling the algif_aead module, e.g. by running echo "install algif_aead /bin/false" > /etc/modprobe.d/disable-algif-aead.conf && rmmod algif_aead 2>/dev/null Even the...