Knowledge Base

Unable to update Plesk with error: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY

Unable to update Plesk on a Debian-like OS with the error below:

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://autoinstall.plesk.com/RUBY_0.0.2 buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E
W: Failed to fetch http://autoinstall.plesk.com/RUBY_0.0.2/dists/buster/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E
Plesk admin may receive an email with the following content:

INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
ERROR:
ERROR: Exited with returncode 1.

Product issue:

#PPPM-14016 "The Plesk GPG key no longer disappears from the /etc/apt/trusted.gpg.d/ directory after installing or updating Plesk."
Fixed in:
- Plesk Obsidian 18.0.54 18 July 2023 (Linux)
- Plesk Obsidian 18.0.53 Update 1 13 June 2023 (Linux)

Please use workaround below to fix the issue and then update the server to prevent this from happening again:

If update is not possible for some reason you may try the following

Connect to the server via SSH.
Fetch and install the Plesk GPG key:

# curl -sS http://autoinstall.plesk.com/plesk.gpg | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/plesk.gpg
# chmod a+rx /etc/apt/trusted.gpg.d && chmod a+r /etc/apt/trusted.gpg.d/plesk.gpg
Apply updates via Tools & Settings > Updates or via Tools & Settings > System Updates.