[ERROR] Node.js 14.x Installation fail

[testmuruga]

Below is the code I used to install Node.js 14 in Docker. It worked properly until January 19, 2026. On January 20, 2026, I began encountering the issue shown below; please review and provide an update.

RUN curl -sL https://deb.nodesource.com/setup_14.x | bash - RUN apt-get -y install nodejs

Error:

W: GPG error: https://deb.nodesource.com/node_14.x jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY
E: The repository 'https://deb.nodesource.com/node_14.x jammy InRelease' is not signed.

[xetrics]

Also running into the same issue with Node 14.x, inside of an Ubuntu 20.04 Focal docker image.

153.1 ## Running `apt-get update` for you...
153.1
153.1 + apt-get update
153.4 Get:1 https://deb.nodesource.com/node_14.x focal InRelease [4583 B]
153.4 Err:1 https://deb.nodesource.com/node_14.x focal InRelease
153.4   The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1655A0AB68576280
153.6 Hit:2 http://archive.ubuntu.com/ubuntu focal InRelease
153.6 Hit:3 http://security.ubuntu.com/ubuntu focal-security InRelease
153.8 Hit:4 http://archive.ubuntu.com/ubuntu focal-updates InRelease
154.0 Hit:5 http://archive.ubuntu.com/ubuntu focal-backports InRelease
154.1 Reading package lists...
155.4 W: GPG error: https://deb.nodesource.com/node_14.x focal InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1655A0AB68576280
155.4 E: The repository 'https://deb.nodesource.com/node_14.x focal InRelease' is not signed.
155.4 Error executing command, exiting

We also tried the steps mentioned in #1181 to no success.

[andormt]

Hey,

I'm also experiencing same error:
Hit:6 http://security.ubuntu.com/ubuntu jammy-security InRelease
Err:5 https://deb.nodesource.com/node_19.x jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1655A0AB68576280
Reading package lists...
W: GPG error: https://deb.nodesource.com/node_19.x jammy 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_19.x jammy InRelease' is not signed.
Error executing command, exiting
The command '/bin/sh -c curl -sL https://deb.nodesource.com/setup_19.x | bash -' returned a non-zero code: 1

3 days ago it was working so probably latest commit (c6e581b) broke it.

[joaomiguelfranco]

Same issue here. I'm not adding anything new, but hoping that with more comments it becomes more visible and increases the priority.

[siegmund-heiss-ich]

Same issue here.

[andormt]

for now I managed to workaround it with using the tarball version instead of the apt repository:
curl -fsSL https://nodejs.org/dist/v19.9.0/node-v19.9.0-linux-x64.tar.xz | tar -xJ -C /usr/local --strip-components=1
at least my deployment pipeline works in this way, maybe it's a help for others

[jurschel-gmt]

This is happening for 12.x as well.

[keenangraham]

Yes, seeing this all the sudden in some old CI tests:

$  sudo apt-get update
Hit:1 https://download.docker.com/linux/ubuntu focal InRelease
Hit:2 http://archive.ubuntu.com/ubuntu focal InRelease                                                                                              
Hit:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease                                                                                      
Hit:4 http://archive.ubuntu.com/ubuntu focal-backports InRelease                                                              
Get:5 https://deb.nodesource.com/node_12.x focal InRelease [4,583 B]                                                          
Hit:6 http://ppa.launchpad.net/git-core/ppa/ubuntu focal InRelease                                                                         
Hit:7 http://security.ubuntu.com/ubuntu focal-security InRelease
Err:5 https://deb.nodesource.com/node_12.x focal 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_12.x focal 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_12.x focal 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.

[Serpent03]

I investigated the issue a bit more, and it looks like the new GPG key signature is different from the expected key signature:

This is the expected key (dated 30 Dec 2025, from archive.org)

$ gpg --show-keys --with-fingerprint testgpg.gpg
pub   rsa4096 2014-06-13 [SC]
      9FD3 B784 BC1C 6FC3 1A8A  0A1C 1655 A0AB 6857 6280
uid                      NodeSource <gpg@nodesource.com>
sub   rsa4096 2014-06-13 [E]

This is the new key (dated around ~20 Jan 2026)

$ gpg --show-keys --with-fingerprint nodesource.gpg.key
pub   rsa2048 2016-05-23 [SC]
      6F71 F525 2828 41EE DAF8  51B4 2F59 B5F9 9B1B E0B4
uid                      NSolid <nsolid-gpg@nodesource.com>
sub   rsa2048 2016-05-23 [E]

If one was to check the digest version, for the first one, it is "2" (SHA-1), and for the second one, it is "10" (SHA2-512), as detailed here on RFC 9580.

We can see that the SHA1 hashing will be considered "unsecure" by Feb 2, 2026: #1908

It seems like nodesource has probably phased this out earlier on their latest key download link, hence the key 1655 A0AB 6857 6280 is not really found anymore.

As others mentioned the solution is probably getting the key from somewhere else.

[JesusPaz]

This is related to our new GPG key. I can make a fix to resolve the issue, but it may take some time. Please remember that we are not actively supporting Node.js 14 because it is not an active LTS version. We strongly recommend migrating to a newer version. You can find more information about Node.js releases here.

[mikhaillopandia]

Hey @JesusPaz
Is the fix for the old Node.js version already made?
We're still facing a problem with https://deb.nodesource.com/setup_10.x