Search results

I got the sane error on a Plesk Obsidian CentOS 7.9 server. The second time I tried after I read this thread I got a warning message, but if I responded with "y" the updates installed. Here is the warning I got (I changed the keys to xxx): Downloading packages: warning...

Switching to OWASP and then back to Atomic Advanced ModSecurity Rules also solved the problem for me, now everything is working as it should, thanks!

TITLE: Atomic ModSecurity ASL errors PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE: Plesk Onyx 17.8.11 Update #18, CentOS Linux 7.5.1804 PROBLEM DESCRIPTION: Starting this night I started getting error emails every hour from Cron on my Plesk server. I am running the latest update both of...

I also have this problems on my servers from around 03:20 CEST today. I am running the Advanced Atomicorp Ruleset (subscription). Turning off and turning on ModSecurity did not help, I'm still getting the same emails with Cron errors every hour saying "Error: ASL has not been configured". Any...

I purchased the advanced Atomic ModSecurity updates from the Plesk store. Everything installed well and seems to be running as it should. However, the updates are broken. Every day I get an error saying that the update of the ModSecurity Atomic filter rules failed. Anyone know how to solve this...

I just finished the update to Onyx successfully and my site is now up and running with the new Plesk Onyx version. Cleaning the cache as you suggested solved my problems. Thanks UFHH01!

My upgrade from 12.5 to Onyx failed and I had to restore a backup to get my site up again asap. Please see the last part of my error log below where the errors are shown. Anyone have any clues on why this upgrade failed? Thanks in advance! - Jonas == Upgrade log == [2017-03-17...

We just updated our Plesk 12.0.18 servers to the just released Centos 7.2. So far everything seems to work well. I will report any issues here. If anyone else has any problems running Plesk on RedHat/Centos 7.2 please let me know.

We are running plesk on a KVM based virtual server. The kvm based server is on an lvm partition that we can create a snapshot of and backup while the server continues to run. This makes it possible to keep a full backup of the entire virtual server on a different physical machine. We also have a...

I'm glad to report that the automatic updates of the Atomic Basic rules seems to have worked well tonight :D. I can now declare my server free of ModSecurity problems for this time. I got very good support from Odin on this. Their response to my ticket was quick, and although the solution given...

I also opened a ticket and got the same reply as you that I should follow https://kb.odin.com/en/127737. However, doing exactly what is said in https://kb.odin.com/en/127737 did not work. First I installed ModSecurity again, since I had uninstalled it. As before installing ModSecurity via the...

I'm glad to hear that you are working on it. I have also created a support ticket with Odin. For everybody's information, here comes a summary of the problems I have had with ModSecurity and what I have tried to do to fix it: 1. The server was up and running fine with ModSecurity using the...

Server online again, I needed to delete a left-over /etc/httpd/conf.d/00_mod_security.conf file that was still there although I had removed ModSecurity. This file prevented httpd to start and brought all of my sites down. In my attempts to solve the ModSecurity Atomic Basic rule problems I...

I've been trying to fix this and now all of a sudden all of the sites on my server are unavailable even though I have removed ModSecurity .... *help please*

I agree that it is the update process that breaks things. The question is why is the update failing?! I had got my server up-and-running again with ModSecurity active by restoring the 50_plesk_basic_asl_rules.conf file from a backup. But then when the update failed a few hours later the...

This morning the ModSecurity rule set update failed again, with the following error message shown in Plesk: Error: Failed to update the ModSecurity rule set: modsecurity_ctl failed: gpg: key 4520AFA9: "Atomicorp (Atomicorp Official Signing Key) <[email protected]>" not changed gpg: Total...

Yea I thought about that also, but then decided not to, upgrading when you have problems is only like asking for more trouble.

Glad to hear that you got your server up and running again. I have also got my server up and running with ModSecurity, you can find the details in the thread linked below. However, if I try to turn off ModSecurity Plesk gives me an error, so something is still not 100% okay. More info in this...

I have continued to investigate this. In my attempts to solve this I had tried to run "aum -u" to manually update the rule-sets. Doing this gives a bunch or errors which I will include below and it also removes the 50_plesk_basic_asl_rules.conf files. # aum -u sh: /sbin/ifconfig: No such file...

I also have a similar problem. I am on Plesk 12.0.18 Update #71 running on an updated CentOS 7.1 KVM based virtual machine. First Plesk all of a sudden gave me an error when it failed to update the rules from Atomic due to a key error. To fix this I tried to remove and reinstall ModSecurity...