How to fix "GPG check FAILED" issue? Unable to update / upgrade!

[Twerybould]

I've been unable to update anything. When I attempt to run sudo dnf update, the process begins as usual but then I encounter the following error:

Check that the correct key URLs are configured for this repository.. Failing package is: brave-browser-1.51.118-1.x86_64
 GPG Keys are configured as:
Public key for brave-keyring-1.11-1.noarch.rpm is not trusted. Failing package is: brave-keyring-1.11-1.noarch
 GPG Keys are configured as:
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: GPG check FAILED

I am trying to install the cPanel / WHM but facing this issue, can anybody help?

 

[JoshuaBolton]

If you're encountering a "GPG check FAILED" error while trying to update your system using sudo dnf update, and specifically seeing errors like:

Error: GPG check FAILED

You're not alone, and the solution is straightforward. This issue typically arises due to a problem with the GPG keys used to verify the packages from a repository. Here's a step-by-step guide to resolving it:

Solution: Bypass the GPG Check Temporarily​

1. Run the Update Command with the --nogpgcheck Option:To bypass the GPG check and proceed with the update, you can use the following command:
   bash
   Copy code
   sudo dnf update --nogpgcheck
   This command tells dnf to skip the GPG check for this update operation.
2. Update the GPG Keys:If you frequently encounter GPG check issues, it might be worth updating or importing the GPG keys for the repositories you are using. Here’s a generic way to import a GPG key (replace the URL with the appropriate key URL for your repository):
   

   sudo rpm --import http://example.com/path/to/gpg/key

3. Clean Cached Packages:Sometimes, clearing the cached packages can help resolve these issues. You can do this by running:
   

   sudo dnf clean packages

Why Use --nogpgcheck?​

Using --nogpgcheck is a temporary solution to get your updates done. It's recommended to identify and fix the underlying GPG key issue to ensure the integrity and security of your package installations. Bypassing GPG checks should be done cautiously and ideally only for trusted sources.
If you continue to face issues, you might want to check the repository configuration files in /etc/yum.repos.d/ and ensure they are correctly set up with the right GPG key URLs.

Example of Repository Configuration​

Here's an example snippet of a repository configuration with a GPG key URL:

[brave-browser]
name=Brave Browser
baseurl=https://brave-browser-rpm-release.s3.brave.com/x86_64/
enabled=1
gpgcheck=1
gpgkey=https://brave-browser-rpm-release.s3.brave.com/brave-core.asc

Ensure that the gpgkey URL is correct and accessible.

Summary​

• Use sudo dnf update --nogpgcheck to bypass the GPG check temporarily.
• Import the correct GPG key for the repository if needed.
• Clean cached packages with sudo dnf clean packages.

Feel free to ask if you have more questions or need further assistance!

 

[Twerybould]

Thank you so much Joshua for replying you are great, my issue is now fixed!