The following signatures couldn't be verified because the public key is not available: NO_PUBKEY

Question

When I run apt-get update, I get this error message:

Err:18 http://dl.google.com/linux/chrome/deb stable Release.gpg                
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6494C6D6997C215E

I understand what causes this issue. I wonder how to fix it.

EDIT:

I tried the most upvoted solution provided in the duplicate link:

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 6494C6D6997C215E

I got this new issue which does not seem to be resolved on this website according to the posts I saw:

Executing: /tmp/tmp.jyolnTyZuJ/gpg.1.sh --keyserver
keyserver.ubuntu.com
--recv-keys
6494C6D6997C215E
gpg: requesting key 997C215E from hkp server keyserver.ubuntu.com
gpg: keyserver timed out
gpg: keyserver receive failed: keyserver error

@Fabby: To me it reads almost exactly the same as the first alternative of karthick87’s. — David Foerster, Dec 23 '18 at 08:18
@DavidFoerster Bowing to the master! :-) Urgh... Cannot retract reopen vote! ;-( — Fabby, Dec 23 '18 at 20:57
That error can also be caused by putting an ASCII-Armored file in /usr/share/keyrings, if you are doing that to avoid using apt-key add as recommended here: https://wiki.debian.org/DebianRepository/UseThirdParty — BCS, Apr 15 '20 at 19:46

Billal Begueradj · Accepted Answer · 2019-01-12T13:28:23.043

186

I want to share what I found here (running over port 80):

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 6494C6D6997C215E

And that was successful:

Executing: /tmp/tmp.BX24beQ8ze/gpg.1.sh --keyserver
hkp://keyserver.ubuntu.com:80
--recv-keys
6494C6D6997C215E
gpg: requesting key 997C215E from hkp server keyserver.ubuntu.com
gpg: key D38B4796: "Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>" 3 new signatures
gpg: key D38B4796: "Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>" 1 new subkey
gpg: Total number processed: 1
gpg:            new subkeys: 1
gpg:         new signatures: 3

I then run sudo apt-get update and everything went fine.

edited Jan 12 '19 at 13:28

answered Aug 06 '17 at 11:07

Billal Begueradj

6,011
11
39
56

2

It looks like your default settings are non-standard. It works for me without specification of a port. – Pilot6 Aug 06 '17 at 11:08
2

@Pilot6 or they're behind a firewall of some sort, so port 11371 is blocked. – muru Aug 08 '17 at 00:44
It works for me without the scheme and port. – Vunb Apr 06 '18 at 02:34
This post https://linuxconfig.org/ubuntu-20-04-gpg-error-the-following-signatures-couldn-t-be-verified helped me before I could find this one. – Arvind K. Sep 25 '20 at 12:20
Doesn't want to import that key it says it already exists. – Sephethus Nov 05 '22 at 17:04

The following signatures couldn't be verified because the public key is not available: NO_PUBKEY

1 Answers1

Linked