Solved “NO_PUBKEY” Error

View Categories

Solved “NO_PUBKEY” Error

2 min read

Issue Description #

When attempting to update the RELIANOID system using the noid-updater, checkupdates, checkupgrades or apt update command, you may encounter the following error message:

root@noid-01:~# noid-updater
Hit:1 https://repo.relianoid.com/ce/v7 bookworm InRelease
Err:1 https://repo.relianoid.com/ce/v7 bookworm InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5CC37ED135C46EB4
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repo.relianoid.com/ce/v7 bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5CC37ED135C46EB4
W: Failed to fetch https://repo.relianoid.com/ce/v7/dists/bookworm/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5CC37ED135C46EB4
W: Some index files failed to download. They have been ignored, or old ones used instead.

Cause #

This issue was introduced in the RELIANOID Community Edition due to a missing dependency in the relianoid package. Specifically, the relianoid-keyring package was not included as a required dependency, causing the system to lack the necessary GPG key for repository authentication.

Solution #

If the Load Balancer Has Internet Access #

Execute the following command to download and install the GPG key:

wget -O - https://repo.relianoid.com/public/relianoid.asc > /etc/apt/trusted.gpg.d/relianoid.asc

If the Load Balancer Does Not Have Internet Access #

Download the key file from a system with internet access. Then, Transfer the file to the load balancer using SCP, SFTP, or any available transfer method. Copy the file to the correct location on the load balancer:

cp relianoid.asc /etc/apt/trusted.gpg.d/relianoid.asc

Verify the Fix #

Once the key is added, update the system again:
apt update
or
noid-updater

If the update completes successfully without the NO_PUBKEY error, the issue is resolved.

Conclusion #

This error occurs due to a missing keyring package in RELIANOID Community Edition. Manually adding the GPG key allows the package manager to verify and retrieve updates properly. Future updates of RELIANOID should include this dependency by default to prevent this issue from recurring.

SHARE ON:

Powered by BetterDocs