Recent content by Bitpalast

  1. Bitpalast

    Issue [BUG] sw-nginx 1.30.1 (CVE-2026-42945 patch) crashes with SIGABRT on AlmaLinux 9.7 + OpenSSL 3.5.1

    It has not here on Alma 8 updates from 18.0.77 to 18.0.78. But maybe it does so on Alma 9???
  2. Bitpalast

    Issue [BUG] sw-nginx 1.30.1 (CVE-2026-42945 patch) crashes with SIGABRT on AlmaLinux 9.7 + OpenSSL 3.5.1

    @Sebahat.hadzhi --> True? We would not want HTTP/3 as this would need a lot of changes in iptables rules as it's not using TCP, but UDP.
  3. Bitpalast

    Question goAccess in 18.0.77

    An update to @Azurel 's plausible suggestion to exclude the /plesk-stat/ directory from ModSecurity. To achieve this, one simple solution is to place the <Location "/plesk-stat/"> SecRuleEngine Off </Location> part into the Tools & Settings > Security > Web Application Firewall...
  4. Bitpalast

    Issue Backup creation to remote FTP storage fails due to local disk space check

    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...
  5. Bitpalast

    Resolved CVE-2026-42945 Nginx Rift and older Wordpress Toolkit heads up

    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
  6. Bitpalast

    Question goAccess in 18.0.77

    Comodo (free) running on Apache (ModSecurity 2.9)
  7. Bitpalast

    Question goAccess in 18.0.77

    Where did you add your lines?
  8. Bitpalast

    Question goAccess in 18.0.77

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

    Question goAccess in 18.0.77

    @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...
  10. Bitpalast

    Resolved Frequent failures on update attempts of ImunifyAV updates, e.g. rustbolit-*.*.rpm

    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...
  11. Bitpalast

    Resolved Frequent failures on update attempts of ImunifyAV updates, e.g. rustbolit-*.*.rpm

    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.
  12. Bitpalast

    Resolved Frequent failures on update attempts of ImunifyAV updates, e.g. rustbolit-*.*.rpm

    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...
  13. Bitpalast

    Question Does Plesk PHP use any of the /opt/plesk/php/<version>/etc/php.ini files?

    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?
  14. Bitpalast

    Question CVE-2026-23918, CVE-2026-24072 and update to Apache 2.4.67

    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...
  15. Bitpalast

    Question CVE-2026-23918, CVE-2026-24072 and update to Apache 2.4.67

    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.
Back
Top