• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Issue Atomic Advanced ~ Unable to get Rulesets

JeffreyReed

New Pleskian
Server operating system version
AlmaLinux 9.6
Plesk version and microupdate number
Plesk Obsidian 18.0.73.3
Hey Everyone,

We’ve been troubleshooting an issue where ModSecurity simply refuses to trigger or apply the Atomic Advanced Ruleset on our Plesk Obsidian (latest build) server running AlmaLinux 9. The license is active and confirmed under Tools & Settings → Web Application Firewall, set to “Atomic Advanced (bought from Plesk)” with the mode set to “On (Blocking)”.

We can ping and trace ka.plesk.com successfully, and have already tried:
  • Disabling and re-enabling ModSecurity multiple times
  • Switching between OWASP, Comodo, and Atomic rulesets
  • Restarting Apache and Nginx
  • Running plesk sbin modsecurity_ctl --apply-config, --enable-ruleset --ruleset atomic, and similar commands
  • Re-authenticating the Atomic vendor login
  • Resetting the ModSecurity configuration completely

Despite all that, the Atomic ruleset never appears as installed —
plesk sbin modsecurity_ctl --ruleset-installed --ruleset atomic returns not installed, and trying to install it results in MODSEC_VENDOR_LOGIN exit status 1.

We’ve verified outbound connectivity, confirmed the Plesk license is active, and validated that the server can reach both Plesk and Atomic endpoints. At this point, it feels like Plesk isn’t actually pulling the ruleset from Atomic even though the license is valid.

Additionally, while troubleshooting, ModSecurity broke our debug/logging folder entirely — we had to fully disable and re-enable ModSecurity just to restore logging functionality.

Has anyone run into this recently on AlmaLinux 9 or found a workaround to get the Atomic Advanced ruleset to actually download and trigger correctly? Any insight or experience would be greatly appreciated!

I see in the logs as well that it says AtomicRuleset but I don't see it applied within my server itself.
Some logs:
Producer: ModSecurity for Apache/2.9.12 (http://www.modsecurity.org/); AtomicRuleset.
Server: Apache
Engine-Mode: "ENABLED"

Thanks
Jeffrey Reed Jr.
 

Attachments

  • 1761082965139.png
    1761082965139.png
    42.3 KB · Views: 2
  • 1761082969038.png
    1761082969038.png
    37.9 KB · Views: 2
  • 1761083496699.png
    1761083496699.png
    57.1 KB · Views: 2
  • 1761083511390.png
    1761083511390.png
    109.1 KB · Views: 2
  • 1761083658853.png
    1761083658853.png
    22.5 KB · Views: 2
I tried multiple commands to search for it, but it currently doesn't exist in our Plesk environment. Is there another location for this, or is this the only location? I didn't need to create an account when purchasing the plugin through the Plesk environment, so why would I need a random account from a file to have this work?
 
The file should be present even if the license is bought from Plesk. I just wanted to verify if there's a connection issue between the server and Atomicorp. However, since it is not present on the server there's likely a different issue than what I suspected. Could you please get in touch with customer support so they can check for potential issue with the license:

 
Back
Top