https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyNjU0IiwiaGFzaCI6ImU4MTA1ZWJlLTYwMjUtNDRjOC05NDc0LTlhNzY0OTI4ZDE4MCJ9
1-800-691-1991 | 9am - 8pm ET
EN

Veeam repository update fails, GPG key error

Challenge

When attempting to update the Veeam Agent for Linux or veeam-release repository package, an error is encountered:
 
GPG key signature on key http://repository.veeam.com/keys/RPM-GPG-KEY-VeeamSoftwareRepo.asc does not match CA Key for repo: veeam

or
 
The following signatures were invalid: EXPKEYSIG 54706D7C5A382FCD Veeam Software Repository key support@veeam.com

Cause

Veeam repository GPG key has changed, import of a new key is required.

Solution

To resolve this issue please install new GPG keys manually.

For .deb based distributions:
curl http://repository.veeam.com/keys/veeam.gpg | apt-key add

For .rpm based distributions:
rpm --import http://repository.veeam.com/keys/RPM-EFDCEA77

 

More information

Alternatively you can download and install the updated veeam -release package from the website or from the repository.
KB ID:
2654
Product:
Veeam Agent for Linux
Version:
VAL 2.0 and below
Published:
2018-05-17
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later