Veeam Backup for Salesforce Built-In Updater Not Finding Updates
Oops! Something went wrong.
Please, try again later.
Challenge
Cause
The updater fails to identify new updates as being available because of an expired or incorrect GPG key used to verify package integrity. Without the proper GPG key, the package manager cannot authenticate or apply updates correctly, resulting in errors during update attempts.
When this occurs, the Veeam-updater.log will contain the following error:
Service.CheckUpdates: Cannot find any updates for VBSF repository (<guid>): packageManagerErrorFailedGetList veeam-repo exit code: 1, timeout exceeded: false, output: , errors: Error: Failed to download metadata for repo 'veeam-repo': repomd.xml GPG signature verification error: Bad GPG signature
Error: Failed to download metadata for repo 'veeam-repo': repomd.xml GPG signature verification error: Bad GPG signature
Solution
Use the following scripts to switch to the correct GPG key:
For RPM-Based Systems (ex:RHEL)
- Download the script:
- Run the script:
- Check for updates once again via Veeam Backup for Salesforce Updater.
For DEB-Based Systems (ex:Ubuntu)
- Download the script:
- Run the script:
- Check for updates once again via Veeam Backup for Salesforce Updater.
More Information
Newer versions of Veeam Backup for Salesforce handle updating the repo GPG keys more effectively, which is why this issue eclusively affects Veeam Backup for Salesforce version 1.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.