TRY NOW
book meeting
BACK TO KB LIST

Veeam Agent for Linux: Update Blocked by Repository Signing Key Change

KB ID: 4836
Product: Veeam Agent for Linux | 6.3 | 6.3.1 | 6.3.2
Published: 2026-03-17
Last Modified: 2026-03-17
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 intended for customers managing Veeam Agent for Linux 6.3 deployments.

Deployments that have already been updated to Veeam Agent for Linux 13, or are being updated to it, are not affected by the repository GPG key change.

Challenge

When attempting to update Veeam Agent for Linux to the latest patch 6.3.2.1307 the update fails during with GPG verification errors, preventing access to the Veeam repository and blocking the agent upgrade.

Debian-base Error Example:

NO_PUBKEY C5A1CF329BB5AC67
The repository 'https://repository.veeam.com/backup/linux/agent/dpkg/debian/public stable InRelease' is not signed.
Updating from such a repository can't be done securely, and is therefore disabled by default.

Cause

This occurs because the repository signing key used for the Linux agent repository was rotated.

  • The previous signing key was nearing expiration (2026‑03‑15).
  • Veeam replaced the key and moved fully to SHA‑256–based signing.
  • Systems that already had the old key installed did not automatically receive the new public key.
  • As a result, package managers can no longer verify the repository metadata and blocks updates for security reasons.

Solution

To resolve this update the veeam-release package, which installs the new repository public key.

For Debian-based Deployments

Download and install the updated release package manually:

wget https://repository.veeam.com/backup/linux/agent/dpkg/debian/public/pool/veeam/v/veeam-release-deb/veeam-release-deb_1.0.11_amd64.deb
sudo dpkg -i veeam-release-deb_1.0.11_amd64.deb
sudo apt update
After this, the repository signature will validate correctly, and the agent can be updated to 6.3.2.1307 without errors. 
sudo apt-get upgrade veeam

For Deployments on RHEL 7

sudo yum install https://repository.veeam.com/backup/linux/agent/rpm/el/7/x86_64/veeam-release-el7-1.0.11-1.x86_64.rpm
sudo yum update veeam

For Deployments on RHEL 8

sudo yum install https://repository.veeam.com/backup/linux/agent/rpm/el/8/x86_64/veeam-release-el8-1.0.11-1.noarch.rpm
sudo yum update veeam

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
Start using Veeam:
Download the product
&
Activate the license key
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.