Install fails due to GPG key not found #785

eddy-geek · 2019-01-18T10:42:11Z

On running sudo apt-get update, the following occurs:

Reading package lists... Done

W: GPG error: https://deb.nodesource.com/node_10.x cosmic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1655A0AB68576280

This can be fixed with:

curl --silent https://deb.nodesource.com/gpgkey/nodesource.gpg.key | sudo apt-key add -

This could be integrated in the manual instructions & the one-line setup script.

The text was updated successfully, but these errors were encountered:

chrislea · 2019-01-18T16:52:13Z

That's already noted in both the manual installation instructions and the setup script. Hope this helps.

700software · 2021-05-10T18:35:23Z

That link is out of date. I think @chrislea is referring to:

distributions/deb/setup_10.x

Line 278 in 0a7ddca

    
           exec_cmd 'curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add -'

suntong · 2021-05-12T02:13:32Z

I'm still getting the above problem:

$ curl -sL https://deb.nodesource.com/setup_14.x | sudo -E bash -

## Installing the NodeSource Node.js 14.x repo...

## Confirming "buster" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_14.x/dists/buster/Release'

## Adding the NodeSource signing key to your keyring...

+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | gpg --dearmor | tee /usr/share/keyrings/nodesource.gpg >/dev/null

## Creating apt sources list file for the NodeSource Node.js 14.x repo...

+ echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_14.x buster main' > /etc/apt/sources.list.d/nodesource.list
+ echo 'deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_14.x buster main' >> /etc/apt/sources.list.d/nodesource.list

## Running `apt-get update` for you...

+ apt-get update
Hit:1 http://ftp.debian.org/debian buster-backports InRelease
. . .
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1655A0AB68576280
Reading package lists... Done                                                                                                                                 
W: GPG error: https://deb.nodesource.com/node_14.x buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1655A0AB68576280
E: The repository 'https://deb.nodesource.com/node_14.x buster InRelease' is not signed.


$ curl --silent https://deb.nodesource.com/gpgkey/nodesource.gpg.key | sudo apt-key add -
OK

$ sudo apt update
Hit:1 http://deb.debian.org/debian buster InRelease
Hit:2 http://deb.debian.org/debian buster-updates InRelease                      
Hit:3 http://security.debian.org/debian-security buster/updates InRelease        
Hit:4 http://ftp.debian.org/debian buster-backports InRelease                                     
Hit:5 http://deb.debian.org/debian bullseye InRelease                                             
Hit:6 http://deb.debian.org/debian bullseye-updates InRelease               
Hit:7 http://ftp.debian.org/debian bullseye-backports InRelease             
Get:8 https://deb.nodesource.com/node_14.x buster InRelease [4584 B]        
Err:8 https://deb.nodesource.com/node_14.x buster InRelease                                                                                                  
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1655A0AB68576280
Reading package lists... Done                                                                                                                                
W: GPG error: https://deb.nodesource.com/node_14.x buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1655A0AB68576280
E: The repository 'https://deb.nodesource.com/node_14.x buster InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

How to fix the problem? thx

PS. The machine is WSL within Win10 accessing Internet behind corp man-in-the-middle (MitM) firewall.

geonanorch · 2021-10-12T16:17:25Z

I have the same issue: started with a fresh Debian 11.0 image, ran the nodesource_setup.sh script and got exactly the error reported in the previous comment by @suntong...

I verified that the key was properly installed by the script:

# gpg --no-default-keyring --keyring /usr/share/keyrings/nodesource.gpg --list-keys
gpg: directory '/root/.gnupg' created
gpg: /root/.gnupg/trustdb.gpg: trustdb created
/usr/share/keyrings/nodesource.gpg
----------------------------------
pub   rsa4096 2014-06-13 [SC]
      9FD3B784BC1C6FC31A8A0A1C1655A0AB68576280
uid           [ unknown] NodeSource <gpg@nodesource.com>
sub   rsa4096 2014-06-13 [E]

And the APT setup seems fine as well:

# cat /etc/apt/sources.list.d/nodesource.list
deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_14.x bullseye main
deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_14.x bullseye main

I suggest a reopen.

WORKAROUND: edit nodesource.list above and add allow-insecure=yes:

deb [ signed-by=/usr/share/keyrings/nodesource.gpg allow-insecure=yes ] https://deb.nodesource.com/node_14.x bullseye main
deb-src [ signed-by=/usr/share/keyrings/nodesource.gpg allow-insecure=yes ] https://deb.nodesource.com/node_14.x bullseye main

JavrelWork · 2021-10-13T12:23:57Z

also having same problem, verified key exists like geonanorch going to try his workaround

dieulot · 2021-11-10T22:21:13Z

The correct (not insecure) solution has been posted in another issue: #1181 (comment)

chmod +r "/usr/share/keyrings/nodesource.gpg"

(I had the same problem on Debian 11. This issue (#785) is the first result on Google for that error.)

jmanteigueiro · 2022-03-18T18:14:18Z

chmod +r "/usr/share/keyrings/nodesource.gpg"

This was the solution for me as well, but +r did not work.

I had to use chmod 644

geonanorch · 2022-03-18T18:17:26Z

something is missing in that command, probably chmod a+r /usr/share/keyrings/nodesource.gpg was meant.

suntong · 2022-03-19T14:01:43Z

This was the solution for me as well, but +r did not work.

Confirmed. Should be chmod a+r.

M0hammedImran · 2022-06-08T09:56:09Z

I was facing this issue when I cancelled the installation process in progress.
Deleting /etc/apt/sources.list.d/nodesource.list and running the install script again worked.

Added 'chmod' step for downloaded keyring file in #debmanual section. Without this, apt(-get) will complain: see issue nodesource#785 .

nrdvana · 2022-08-12T06:03:45Z

Please add the chmod a+r to the official instructions. I just wasted an hour on this.

netik · 2022-08-30T23:00:22Z

You can also add the key from ubuntu...

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 1655A0AB68576280

baozitao · 2022-09-25T15:32:45Z

@

I was facing this issue when I cancelled the installation process in progress. Deleting /etc/apt/sources.list.d/nodesource.list and running the install script again worked.

good job, it worked!!

jotakar · 2022-12-21T23:17:24Z

Hi, I have a similar issue. I can add the repository but I cannot use it. I got installed nodejs always.
I do:
curl -fsSL https://deb.nodesource.com/setup_16.x | bash -
I get :

## Installing the NodeSource Node.js 14.x repo...

## Populating apt-get cache...

+ apt-get update
Obj:1 http://security.debian.org/debian-security bullseye-security InRelease
Obj:2 http://deb.debian.org/debian bullseye InRelease                                                                     
Obj:3 http://deb.debian.org/debian bullseye-updates InRelease                                                             
Obj:4 https://dl.yarnpkg.com/debian stable InRelease                                                
Obj:5 https://deb.nodesource.com/node_14.x bullseye InRelease             
Leyendo lista de paquetes... Hecho

## Confirming "bullseye" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_14.x/dists/bullseye/Release'

## Adding the NodeSource signing key to your keyring...

+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | gpg --dearmor | tee /usr/share/keyrings/nodesource.gpg >/dev/null

## Creating apt sources list file for the NodeSource Node.js 14.x repo...

+ echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_14.x bullseye main' > /etc/apt/sources.list.d/nodesource.list
+ echo 'deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_14.x bullseye main' >> /etc/apt/sources.list.d/nodesource.list

## Running `apt-get update` for you...

+ apt-get update
Obj:1 http://security.debian.org/debian-security bullseye-security InRelease
Obj:2 http://deb.debian.org/debian bullseye InRelease                                                                      
Obj:3 http://deb.debian.org/debian bullseye-updates InRelease                                                              
Obj:4 https://deb.nodesource.com/node_14.x bullseye InRelease                                                              
Obj:5 https://dl.yarnpkg.com/debian stable InRelease                                             
Leyendo lista de paquetes... Hecho

## Run `sudo apt-get install -y nodejs` to install Node.js 14.x and npm
## You may also need development tools to build native addons:
     sudo apt-get install gcc g++ make
## To install the Yarn package manager, run:
     curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | gpg --dearmor | sudo tee /usr/share/keyrings/yarnkey.gpg >/dev/null
     echo "deb [signed-by=/usr/share/keyrings/yarnkey.gpg] https://dl.yarnpkg.com/debian stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
     sudo apt-get update && sudo apt-get install yarn`

No error. And the file nodesource.list is in the sources.list.d folder.
But when I write
apt-cache policy nodejs

I get following result

nodejs:  

  Instalados: (ninguno)  

  Candidato:  12.22.12~dfsg-1~deb11u1  

  Tabla de versión:  

     12.22.12~dfsg-1~deb11u1 500  

        500 http://security.debian.org/debian-security bullseye-security/main i386 Packages  

     12.22.5~dfsg-2~11u1 500  

        500 http://deb.debian.org/debian bullseye/main i386 Packages  `

So it looks like it doesn't read the nodesource.list repository!!, is the source disabled? how to enable?
Where is the error?
Thanks

JesusPaz · 2023-01-02T18:37:08Z

the necessary line has already been added to the documentation #1494

chrislea closed this as completed Jan 18, 2019

JesusPaz reopened this Mar 18, 2022

This was referenced Mar 19, 2022

Add Aliyun Linux 2 support #1046

Closed

jibing57:carl_aliyun_linux_support@###jibing5 #1356

Closed

Ghepardo added a commit to Ghepardo/distributions that referenced this issue Jul 8, 2022

Update README.md

369b112

Added 'chmod' step for downloaded keyring file in #debmanual section. Without this, apt(-get) will complain: see issue nodesource#785 .

Ghepardo mentioned this issue Jul 8, 2022

Update README.md #1417

Closed

jmiranda mentioned this issue Jul 18, 2022

Docker failing to build openboxes/openboxes-docker#14

Closed

JesusPaz closed this as completed Jan 2, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Install fails due to GPG key not found #785

Install fails due to GPG key not found #785

eddy-geek commented Jan 18, 2019

chrislea commented Jan 18, 2019

700software commented May 10, 2021

suntong commented May 12, 2021 •

edited

Loading

geonanorch commented Oct 12, 2021 •

edited

Loading

JavrelWork commented Oct 13, 2021 •

edited

Loading

dieulot commented Nov 10, 2021

jmanteigueiro commented Mar 18, 2022

geonanorch commented Mar 18, 2022

suntong commented Mar 19, 2022

M0hammedImran commented Jun 8, 2022

nrdvana commented Aug 12, 2022

netik commented Aug 30, 2022 •

edited

Loading

baozitao commented Sep 25, 2022

jotakar commented Dec 21, 2022 •

edited

Loading

JesusPaz commented Jan 2, 2023

Install fails due to GPG key not found #785

Install fails due to GPG key not found #785

Comments

eddy-geek commented Jan 18, 2019

chrislea commented Jan 18, 2019

700software commented May 10, 2021

suntong commented May 12, 2021 • edited Loading

geonanorch commented Oct 12, 2021 • edited Loading

JavrelWork commented Oct 13, 2021 • edited Loading

dieulot commented Nov 10, 2021

jmanteigueiro commented Mar 18, 2022

geonanorch commented Mar 18, 2022

suntong commented Mar 19, 2022

M0hammedImran commented Jun 8, 2022

nrdvana commented Aug 12, 2022

netik commented Aug 30, 2022 • edited Loading

baozitao commented Sep 25, 2022

jotakar commented Dec 21, 2022 • edited Loading

JesusPaz commented Jan 2, 2023

suntong commented May 12, 2021 •

edited

Loading

geonanorch commented Oct 12, 2021 •

edited

Loading

JavrelWork commented Oct 13, 2021 •

edited

Loading

netik commented Aug 30, 2022 •

edited

Loading

jotakar commented Dec 21, 2022 •

edited

Loading