Articles in this section

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

Atif Bangash
Updated
Plesk for Linux kb: technical ABT: Group A

Applicable to:

  • Plesk for Linux

Symptoms

  • Debian or Ubuntu is installed on the server.

  • Plesk updates or some extensions installation fail with the following message:

    PLESK_ERROR: An error occurred on attempt to install packages.
    Attention! Your software might be inoperable.
    Please contact product technical support.

  • Following warning message could be found in /var/log/plesk/install/autoinstaller3.log:

    CONFIG_TEXT: W: GPG error: http://repo.cloudlinux.com/kernelcare-debian/8 stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DC3D600CDEF74BB

    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://us-west-2.ec2.archive.ubuntu.com/ubuntu xenial-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32

    CONFIG_TEXT: Executing: /tmp/apt-key-gpghome.dhoA48mqwL/gpg.1.sh --keyserver hkp://ha.pool.sks-keyservers.net:80 --recv-keys 58118E89F3A912897C070ADBF76221572C52609D
    , stderr: Warning: apt-key output should not be parsed (stdout is not a terminal)
    gpg: key F76221572C52609D: 7 signatures not checked due to missing keys

Cause

Required public keys are missing.

Resolution

  1. Login to the server via SSH.
  2. Add missing keys by executing the following command for each key from the log file, for example (the actual key server name and the key mentioned in the error message should be used in the command above):

    • For Ubuntu 22 and 24 the following commands should be used:

      # gpg --keyserver keyserver.ubuntu.com --recv-keys 6DC3D600CDEF74BB

    • For older versions of Ubuntu/Debian

      # sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys F76221572C52609D
      # sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 40976EAF437D05B5
      # sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 6DC3D600CDEF74BB
      # sudo apt-key adv --keyserver hkp://ha.pool.sks-keyservers.net:80 --recv-keys F76221572C52609D

  3. Clean APT cache:

    # apt-get clean

Was this article helpful?

Comments

5 comments
Date Votes
  • Avatar
    Philip Stanton

    Keys not found at any of the addresses.

    0
  • 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
  • Avatar
    B3 Support 
    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
  • Avatar
    Julian Bonpland Mignaquy

    hi B3 Support we are actively investigating this issue with our developers.

    0
  • Avatar
    Timo Meinen

    This helped for me: https://support.plesk.com/hc/en-us/articles/13499261313303-Unable-to-update-Plesk-with-error-The-following-signatures-couldn-t-be-verified-because-the-public-key-is-not-available-NO-PUBKEY

    0

Please sign in to leave a comment.