kb: technical
Applicable to:
- Plesk for Linux
Symptoms
Cannot enable ModSecurity Atomicorp ruleset in Plesk on Debian-like installations with the following error in UI:
PLESK_ERROR: 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.
Cause
Package manager is missing the required GPG key.
Resolution
1. Log in to Plesk via SSH
2. Install the key with the following CLI command:
apt-key adv --keyserver keyserver.ubuntu.com --recv-key FFBD5D0A4520AFA9
Comments
5 comments
Hi.
I had launched command in ssh session and i get an error:
root@xxxxxxxxx:/home/adminsystem# apt-key adv --keyserver keyserver.ubuntu.com --recv-key FFBD5D0A4520AFA9
Executing: /tmp/apt-key-gpghome.RlyS4xbpT8/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-key FFBD5D0A4520AFA9
gpg: key FFBD5D0A4520AFA9: "Atomicorp (Atomicorp Official Signing Key) <support@atomicorp.com>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
root@xxxxxxxxx:/home/adminsystem# apt-get update && apt-get upgrade
…
Ign:22 https://updates.atomicorp.com/channels/tortix-common/ubuntu bionic InRelease
Get:23 https://updates.atomicorp.com/channels/tortix-common/ubuntu bionic Release [3360 B]
Get:24 https://updates.atomicorp.com/channels/tortix-common/ubuntu bionic Release.gpg [866 B]
Ign:24 https://updates.atomicorp.com/channels/tortix-common/ubuntu bionic Release.gpg
Reading package lists... Done
W: GPG error: https://updates.atomicorp.com/channels/tortix-common/ubuntu bionic Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FFBD5D0A4520AFA9
E: The repository 'https://updates.atomicorp.com/channels/tortix-common/ubuntu bionic Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Diputación de Málaga Informática y sistemas
The issue hasn't been reproduced on a test server. Please create a request to Plesk Technical support to investigate it.
I have the same problem here on my server.
Adding the keys as described above brings up exactly the same error messages.
Is there already a solution to this?
Description: Ubuntu 18.04.6 LTS
Release: 18.04
Codename: bionic
I get the same error message. Are there any new findings on this?
Executing: /tmp/apt-key-gpghome.OltpFkL0gd/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-key FFBD5D0A4520AFA9
gpg: Schlüssel FFBD5D0A4520AFA9: "Atomicorp (Atomicorp Official Signing Key) <support@atomicorp.com>" nicht geändert
gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1
gpg: unverändert: 1
I also got this error:
W: GPG error: https://updates.atomicorp.com/channels/tortix-common/debian bookworm Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FFBD5D0A4520AFA9
E: The repository 'https://updates.atomicorp.com/channels/tortix-common/debian bookworm Release' is not signed.
The error occurred after OS upgrade from Debian 10 to Debian 12.
Please sign in to leave a comment.