How to Manually Update GPG key on Veeam Hardened Repository Appliance

KB ID: 4833
Product: Veeam Backup & Replication | 12.3 | 12.3.1 | 12.3.2
Published: 2026-03-16
Last Modified: 2026-03-16
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Article Applicability

This article is specifically regarding the Veeam Hardened Repository ISO v2 appliance, which was distributed alongside Veeam Backup & Replication 12.

For information about manually updating the GPG key on the appliances associated with Veeam Backup & Replication 13, review KB4834.

Challenge

This article documents how to manually update the GPG key for Veeam Hardened Repository ISO v2 appliances.

Generally, the new key should automatically be distributed to all appliances that have access to the Veeam repository. However, if the appliance does not have access to the repository (either directly, via a mirror, or via http_proxy), the GPG key will not be updated. After the installed GPG expires, that appliance will be unable to connect to the update repository.

On March 15, 2026, the GPG key used to sign the Veeam RPM packages expired.

Solution

  1. Download the new GPG key and copy it to the Veeam Hardened Repository either via the Files node or via SSH using the veeamsvc account.
    The new key is available here:
    https://repository.veeam.com/keys/RPM-E6FBD664
  2. Use Live Boot ISO to gain shell access to the Veeam Hardened Repository appliance.
    Live Boot is available from the same ISO used for installation.
  3. Once in live boot, mount the original system disks and enter chroot.
  4. Delete the old GPG key using the following command:
rpm -qa gpg-pubkey | grep e6fbd664 | xargs -r rpm -e
  1. Import the new GPG key using the following command:
rpm --import /path/to/new/gpg_key
After importing the new GPG key, updates from the repository should be available again.

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.