Search results

[2025-05-19 15:20:44.786] 1427362:682b302ab236f ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/modsecurity_ctl' '--install' '--with-backup' '--apache' '--ruleset' 'tortix'] with exit code [1] [2025-05-19 15:20:46.415] 1427362:682b302ab236f ERR [util_exec] proc_close() failed...

Hello, I have been receiving this error for four days: Error al actualizar el conjunto de reglas de ModSecurity: modsecurity_ctl failed: Error interacting with https://updates.atomicorp.com/pgui_v/dbp.php: HTTP Error 500: Internal Server Error

Very good, community, since the last update I am getting this error every hour.

My folder is not /etc/httpd/conf/modsecurity.d/rules/atomic, it is /etc/httpd/conf/modsecurity.d/rules/tortix Is this correct? The /etc/httpd/conf/modsecurity.d/rules/atomic folder does not exist.

By the way, I have the atomic payment rules but purchased through the plesk store.

The only way I can know if the rules have been updated that I know of is through the notifications, and they no longer appear since the last update. Is there any other way to find out? Another reference I can think of is when I used to run “plesk daily -UpdateModSecurityRuleSet” it took between...

Very strange, because updating the atomic rules from “aum” did not deactivate selinux, but doing it from plesk did. Now activating the rules from aum updates the rules correctly, but doing it from plesk does not update the rules at all. Are you sure nothing is broken in the last update?

they started to appear for me too after upgrading to Plesk Obsidian 18.0.67

Unfortunately it did not work. I never had to put in before: [modSecurity] ruleSet.tortix = true ruleSet.atomic = true in panel.ini, and it always worked, I tried it anyway but it didn't work. I have no error in plesk, and everything works perfectly until I run plesk daily...

Is there no news on this matter? We have had a month with Modsecurity broken in plesk. Something as important as security, I get the feeling that it is not given the attention it should be, and that can bring many problems.

I have manually modified the files /var/awp/etc/config and /var/awp/etc/config.aum by setting MODSEC_ENABLED=“yes” and it works correctly again if I run aum -uf. The rules are updated correctly, but if I run plesk daily UpdateModSecurityRuleSet the rules are not updated and the configuration...

I have the atomic advanced. I really don't see any errors. Just every night when the rules were updated I got a notification in plesk, notifying me of the rules update. That no longer appears. As I found it strange not to have the update, I tried to force it manually with plesk daily -f...

Since the last plesk update the modsecurity updates at least for atomic have stopped working. They don't work neither from plesk's daily cron job nor by forcing it with aum -uf. Running aum -uf gives as a result:

Chatgpt tells me that your version is newer than mine, and that the correct form for that version is this one: dnssec-validation auto; managed-keys-directory "/var/named/dynamic"; the path /var/named/dynamic I don't know if it corresponds to the one on your system.

Did you create that file? I had to create it. If you did it and the error persists I can't help you, see if there is someone on the forum who is more familiar with this.

what errors?

Right, I created that file with nothing in it. The file did not exist on my system.

Follow this path in the plesk interface. Plesk => Tools and Settings => DNS Settings => Server-wide Settings => Additional DNS Settings

follow in your footsteps. The only thing I think I did different from you was to add dns configuration at the server level, in the plesk interface: In the text field I already had: This made it start to work.

More logs confirming that it works as expected. postfix/smtp [1361245] Untrusted TLS connection established with wrong.havedane.net[xx.xx.xxx.xxx.xxx]:25: TLSv1.3 with encryption TLS_AES_256_GCM_SHA384 (256/256 bits) key exchange X25519 server signature RSA-PSS (2048 bits) server digest SHA256...