Articles in this section

See more

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

Avatar
Julian Bonpland Mignaquy
Updated
Follow
kb: bug kb: fixed Plesk for Linux

Symptoms

  • 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.

Cause

Product issue:

Resolution

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

Workaround

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

workaround

  1. Connect to the server via SSH.

  2. 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

  3. Apply updates via Tools & Settings > Updates or via Tools & Settings > System Updates.

Comments

7 comments

Sort by Date Votes
  • Avatar
    Mark-Oliver Wolter

    2.5 Make sure there is a plesk.gpg in /etc/apt/keyrings. If missing, grab it from http://autoinstall.plesk.com/plesk.gpg

    1
    Comment actions Permalink
  • Avatar
    Anastasiia Zyrianova

    Hello Mark-Oliver Wolter,

    Thank you for your comment. The article was updated accordingly.

    0
    Comment actions Permalink
  • Avatar
    Attractive Media

    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.

    0
    Comment actions Permalink
  • Avatar
    Tom Andersen

    I tried all that, still getting the same NO_PUBKEY BD11A6AA914BDF7E error on the SSH command line. There is a chmoded new plesk.gpg file in both /etc/apt/keyrings and /etc/apt/trusted.gpg.d .

    When I use the interface, it says that there are no new Plesk versions (stuck at 18.0.52) - I want to get to 18.0.53 update 1 as I _think_ my smaller servers are falling over and getting stuck while trying to update. (Server hangs - will not allow SSH). This is on 1 - 2GB lightsail servers. Hangs every 24 - 72 hours. I was able to update some of my servers to the latest plesk and they seem to be running better. 

    0
    Comment actions Permalink
  • Avatar
    Tom Andersen

    Interesting. I copied the plesk.gpg file to  /etc/apt/trusted.gpg.d/plesk.gpg - then chmod it. Then in the UI visit the page https://myserver.whatever/admin/server/tools and pick Plesk -> updates and then the file /etc/apt/trusted.gpg.d/plesk.gpg is removed. Is that expected or normal? I'm more of a C/Go/JS/PHP coder than sysadmin. 

    0
    Comment actions Permalink
  • Avatar
    Tom Andersen

    https://talk.plesk.com/threads/no_pubkey-bd11a6aa914bdf7e.368962/ seems relevant. There is a bit by 'Mow' where he points out that things are self sabotaging...

    0
    Comment actions Permalink
  • Avatar
    Tom Andersen

    Also https://support.plesk.com/hc/en-us/articles/12377139806359

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles