All new cases are to be reported in PPS-14261. If there's a server access available, 1st ping the assigned developer before applying a solution. The root cause is required.
Unable to update Plesk on a Debian-like OS with the error below:
CONFIG_TEXT: 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:
CONFIG_TEXT: INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
ERROR: Exited with returncode 1.
Plesk GPG key misconfiguration.
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
Open the repository in question in any text editor, for example, in the vi editor:
# vi /etc/apt/sources.list.d/plesk-ext-ruby.list
Add the missing
signed-bysection to the file as below:
CONFIG_TEXT: deb [arch=amd64 signed-by=/etc/apt/keyrings/plesk.gpg] http://autoinstall.plesk.com/RUBY_0.0.2 buster all
Save the changes and close the file. Re-run Plesk update if required.
2.5 Make sure there is a plesk.gpg in /etc/apt/keyrings. If missing, grab it from
Hello Mark-Oliver Wolter,
Thank you for your comment. The article was updated accordingly.
Tried this solution but for me Imunify360's repos will not acknowledge my adjustments made via the above steps no matter what. I opened a ticket with Plesk Support and will update once we get to a solution in case others face a similar issue.
Please sign in to leave a comment.