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

Follow

Comments

5 comments

  • Avatar
    Frank Rochlitzer
    Err:5 http://autoinstall.plesk.com/KAV_8.5.1 bionic InRelease
      The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E
    Err:6 http://autoinstall.plesk.com/NODE_0.0.2 all InRelease
      The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E
    Reading package lists...
    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/KAV_8.5.1 bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E
    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/NODE_0.0.2 all 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/KAV_8.5.1/dists/bionic/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/NODE_0.0.2/dists/all/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E
    W: Some index files failed to download. They have been ignored, or old ones used instead.
    apt-key adv --keyserver autoinstall.plesk.com --recv-keys BD11A6AA914BDF7E
    Executing: /tmp/apt-key-gpghome.KI8PP0ztEK/gpg.1.sh --keyserver autoinstall.plesk.com --recv-keys BD11A6AA914BDF7E
    gpg: keyserver receive failed: Connection timed out
    plesk sbin pum --check
    2023-04-27 08:46:28 INFO: pum is called with arguments: ['--check']
    2023-04-27 08:46:30 ERROR:
    2023-04-27 08:46:30 ERROR: Exited with returncode 1.
    exit status 1

    This error comes back every 1 to 2 days on different systems.
    How can this problem be eliminated for good?

    0
    Comment actions Permalink
  • Avatar
    Julian Bonpland Mignaquy

    Philip Stanton could you please paste the command you ran here? The actual key server name and the key mentioned in the error message should be used in the command above

    0
    Comment actions Permalink
  • Avatar
    Philip Stanton

    Keys not found at any of the addresses.

    0
    Comment actions Permalink
  • Avatar
    Julian Bonpland Mignaquy

    hi Frank Rochlitzer we are actively investigating this issue with our developers.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request