• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Web Application Firewall: Error when changing to ruleset "Atomic Advanced (erworben über Plesk)"

Sascha Schlüter

New Pleskian
Server operating system version
Debian 10
Plesk version and microupdate number
Version 18.0.60 Update #1
I recently decided to test out the ruleset "Atomic Advanced (erworben über Plesk)" for WAF, but when chaning to this option i get the following error message:

Code:
modsecurity_ctl failed: Failed to install aum: Command '/bin/bash < /tmp/tmpcqqtj8yh/aum' returned non-zero exit status 1. Output: b"\nAtomic Updater Modified (AUM) Installer (v6.4.2)\n  Further Documentation is available at: \n  https://wiki.atomicorp.com/wiki/index.php/Aum\n\n  Support: [email protected]\n\n\nInstalling the Atomic GPG key: \nHit:1 http://security.debian.org buster/updates InRelease\nHit:2 http://deb.debian.org/debian buster InRelease\nHit:3 http://deb.debian.org/debian buster-updates InRelease\nHit:4 http://autoinstall.plesk.com/KAV_8.9.2 buster InRelease\nHit:5 http://autoinstall.plesk.com/pool/PSA_18.0.60_14384 buster InRelease\nHit:6 http://autoinstall.plesk.com/pool/PHP_7.3.33_248 buster InRelease\nHit:7 http://autoinstall.plesk.com/PHP74_17 buster InRelease\nHit:8 http://autoinstall.plesk.com/PHP80_17 buster InRelease\nHit:9 https://autoinstall.plesk.com/grafana/deb stable InRelease\nHit:10 http://autoinstall.plesk.com/PHP81_17 buster InRelease\nHit:11 https://autoinstall.plesk.com/DRWEB_6.0.2.9 buster InRelease\nHit:12 http://autoinstall.plesk.com/PHP82_17 buster InRelease\nHit:13 http://autoinstall.plesk.com/pool/WPB_18.0.55_74 all InRelease\nHit:14 http://autoinstall.plesk.com/pool/WPB_18.0.59_77 all InRelease\nGet:15 https://updates.atomicorp.com/channels/tortix-common/debian buster InRelease [2,497 B]\nErr:15 https://updates.atomicorp.com/channels/tortix-common/debian buster InRelease\n  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FFBD5D0A4520AFA9\nReading package lists...\n\n  ERROR: apt failed to update repodata\n  exiting...\n\n" Errors: b"TERM environment variable not set.\nW: GPG error: https://updates.atomicorp.com/channels/tortix-common/debian buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FFBD5D0A4520AFA9\nE: The repository 'https://updates.atomicorp.com/channels/tortix-common/debian buster InRelease' is not signed.\n"

What can I do to switch to the (already paid) option?
Thank you...
 
Try to install the key via sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-key FFBD5D0A4520AFA9 command.
 
Thank you very much for your help. Unfortunally, this hint did not work, since i get this result:

Executing: /tmp/apt-key-gpghome.EOZMAkXq2K/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-key FFBD5D0A4520AFA9
gpg: key FFBD5D0A4520AFA9: public key "Atomicorp (Atomicorp Official Signing Key) <[email protected]>" imported
gpg: Total number processed: 1
gpg: imported: 1
gpg: no writable keyring found: Not found
gpg: error reading '[stdin]': General error
gpg: import from '[stdin]' failed: General error
gpg: Total number processed: 0

and a new try to switch to the atomic ruleset fails again with the message mentioned above.
 
Did you run the command with root (super user) privileges? I.e as the root user of with sudo?
 
Back
Top