Comprehensive data protection for all workloads
Post Reply
CV_VBR
Influencer
Posts: 10
Liked: 3 times
Joined: May 28, 2025 10:42 pm
Full Name: System Administration
Contact:

[v13] Bad GPG Signature

Post by CV_VBR »

Hello,

We did a test/dev deployment of the v13 appliance and after the update we applied on 10/6 (latest at that time as we were just testing update functionalities/features) we are no longer able to detect updates. It always errors out with "Failed to update package cache: Error: Failed to download metadata for repo 'veeam-backup-external-mandatory': repomd.xml GPG signature verification error: Bad GPG signature". I am not very familiar with Linux, so I am not sure if this is a Linux quick fix issue or something I did via configuration either on the appliance or network/firewall settings although our firewall logs show nothing being blocked and it worked the first time. We have restarted the appliance several times with no difference. If this isn't a "common knowledge" issue/fix, I will submit a support case. I'm hoping it is related to my newbie-ness.

Thank you,
James
Gostev
Chief Product Officer
Posts: 32729
Liked: 7946 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: [v13] Bad GPG Signature

Post by Gostev »

Hello, actually you don't need to know anything about Linux to use Veeam Software Appliance, that's the whole point. And no, this is not a known issue so far, otherwise there would have been a thread here about this already with multiple people reporting the same issue (law of large numbers!). Therefore, unless you see an existing topic, please always start with a support case in future. This way we can have devs start investigating right away, and the first thing they always ask for is a support case with debug logs. Thanks
CV_VBR
Influencer
Posts: 10
Liked: 3 times
Joined: May 28, 2025 10:42 pm
Full Name: System Administration
Contact:

Re: [v13] Bad GPG Signature

Post by CV_VBR »

Hello Gostev,

So, how does one submit a support case for v13 of VBR when that is not an option in my drop downs?

Thank you,
BrianBuchanan
Enthusiast
Posts: 71
Liked: 18 times
Joined: Nov 29, 2019 12:56 pm
Full Name: Brian Buchanan
Contact:

Re: [v13] Bad GPG Signature

Post by BrianBuchanan »

I'm experiencing a similar error on my V13 VSA and all VIA.

Failed to check for updates
Failed to update package cache: Error: Failed to download metadata for repo 'veeam-backup-external-mandatory': repomd.xml GPG signature verification error: Bad GPG signature

The closest I found was this post from March 2024 when the GPG key expired. Maybe it happened again?
veeam-backup-for-salesforce-f65/veeam-r ... 93025.html
Dima P.
Product Manager
Posts: 14937
Liked: 1828 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: [v13] Bad GPG Signature

Post by Dima P. »

So, how does one submit a support case for v13 of VBR when that is not an option in my drop downs?
Try selecting Technical product support and in 'I need support for' select Veeam Software Appliance.
I'm experiencing a similar error on my V13 VSA and all VIA.
Please raise support case and share the case id with us. Thank you!
Gostev
Chief Product Officer
Posts: 32729
Liked: 7946 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: [v13] Bad GPG Signature

Post by Gostev »

CV_VBR wrote: Oct 14, 2025 6:24 pmSo, how does one submit a support case for v13 of VBR when that is not an option in my drop downs?
You submit a support case like you normally would, by selecting Veeam Software Appliance in the "I need support for" dropdown. If you don't see it in dropdown then you're using an account that does not have an appropriate paid license associated. You should contact your Veeam sales representative to resolve it.

P.S. Dima beat me to that.
CV_VBR
Influencer
Posts: 10
Liked: 3 times
Joined: May 28, 2025 10:42 pm
Full Name: System Administration
Contact:

Re: [v13] Bad GPG Signature

Post by CV_VBR »

Hello Dima P.,

"Veeam Software Appliance" is not an option in my support for drop down. The license is valid because it was successfully downloaded and activated with this account/license.

Thank you,
James
Gostev
Chief Product Officer
Posts: 32729
Liked: 7946 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: [v13] Bad GPG Signature

Post by Gostev »

I just checked myself and I do get the option, so it's not a technical issue with the portal but with your account. It's not something we R&D can help with, you will need to contact your Veeam sales rep and have them fix your records.
CV_VBR
Influencer
Posts: 10
Liked: 3 times
Joined: May 28, 2025 10:42 pm
Full Name: System Administration
Contact:

Re: [v13] Bad GPG Signature

Post by CV_VBR »

Hello,

Support case created to be able to create a support case. Once I am able to actually create a support case for the appliance, I will post it here (hopefully next week).

Thank you,
James
Dima P.
Product Manager
Posts: 14937
Liked: 1828 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: [v13] Bad GPG Signature

Post by Dima P. »

James,
"Veeam Software Appliance" is not an option in my support for drop down.
The web team has identified an issue with the Support Portal, it is a corner case affecting certain product licenses. They are working on a fix, please stay tuned for updates.
ashleyw
Veteran
Posts: 254
Liked: 78 times
Joined: Oct 28, 2010 10:55 pm
Full Name: Ashley Watson
Contact:

Re: [v13] Bad GPG Signature

Post by ashleyw »

Seeing exactly the same here since this morning, with all managed servers so it impacts the compliance reporting on the home page of B&R system. Support ticket logged # 07852618. Sadly the "preparing support logs bundle" timed out so I couldn't add bundle to ticket.
"Failed to update package cache: Error: Failed to download metadata for repo 'veeam-backup-external-mandatory': repomd.xml GPG signature verification error: Bad GPG signature
System."
I'm assuming the files that are not signed correctly relate to the following;
https://repository.veeam.com/vsa/9.2/ex ... repomd.xml
https://repository.veeam.com/vsa/9.2/ex ... md.xml.key

https://repository.veeam.com/vsa/9.2/vb ... repomd.xml
https://repository.veeam.com/vsa/9.2/vb ... md.xml.key

https://repository.veeam.com/vsa/9.2/wo ... repomd.xml
https://repository.veeam.com/vsa/9.2/wo ... md.xml.key

thanks
Ashley
Gostev
Chief Product Officer
Posts: 32729
Liked: 7946 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: [v13] Bad GPG Signature

Post by Gostev »

QA has checked everything multiple times both last night and right now and it is still looking good on our side in Europe. Therefore this might be a region-specific issue related to AWS replication. Therefore it will likely resolve itself within 24 hours.

Repository metadata is only signed after we update any packages and then the repository metadata file to reflect the changes made. The updated files must be then replicated across the world. Therefore it possible to run into a situation when your region has already received the new packages and the repository metadata file, but not yet the updated signature file. But this is normal and automated update check retries are there to solve this exact issue.
ashleyw
Veteran
Posts: 254
Liked: 78 times
Joined: Oct 28, 2010 10:55 pm
Full Name: Ashley Watson
Contact:

Re: [v13] Bad GPG Signature

Post by ashleyw »

Thanks, Despite the fact that NZ invented pavlova (don't mention it to our Aussie friends though!), bungy jumping and the electric fence, we seem to get more than our fair share of problems in return - despite the nearest AWS AZ being very close to us!
Is there a way for us to verify if edge caching nodes contain the correct cached artifacts via script? Reason why is I'm also sitting on a page rendering issue that others are struggling to replicate and thought if out of date css/javascript files etc are also been wrongly cached this could potentially explain that as well.

If we still have the gpg issue after 24 hours should I follow up on here?
Gostev
Chief Product Officer
Posts: 32729
Liked: 7946 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: [v13] Bad GPG Signature

Post by Gostev » 1 person likes this post

Yes please.

We will also make a change in 13.0.1 based on this thread to have Veeam Updater retry for much longer before starting to throw errors, as to account for any repository update and/or replication delays.
BrianBuchanan
Enthusiast
Posts: 71
Liked: 18 times
Joined: Nov 29, 2019 12:56 pm
Full Name: Brian Buchanan
Contact:

Re: [v13] Bad GPG Signature

Post by BrianBuchanan » 4 people like this post

Just to follow up, the updater started working for me sometime over night and everything looks good now.
CV_VBR
Influencer
Posts: 10
Liked: 3 times
Joined: May 28, 2025 10:42 pm
Full Name: System Administration
Contact:

Re: [v13] Bad GPG Signature

Post by CV_VBR » 2 people like this post

Hello,

My update checks are now successful as of 42 minutes ago.

Thank you,
James
ashleyw
Veteran
Posts: 254
Liked: 78 times
Joined: Oct 28, 2010 10:55 pm
Full Name: Ashley Watson
Contact:

Re: [v13] Bad GPG Signature

Post by ashleyw » 2 people like this post

thanks guys, working fine for us now. All showing green and we applied the one update to the B&R appliance as well.
quicksilver1663
Novice
Posts: 7
Liked: 1 time
Joined: Oct 09, 2019 1:35 pm
Contact:

Re: [v13] Bad GPG Signature

Post by quicksilver1663 » 1 person likes this post

Still getting this error in Canada as of 7:54am AST
chris.childerhose
Veeam Vanguard
Posts: 678
Liked: 175 times
Joined: Aug 13, 2014 6:03 pm
Full Name: Chris Childerhose
Location: Toronto, ON
Contact:

Re: [v13] Bad GPG Signature

Post by chris.childerhose »

Still seeing this error here in Toronto, Canada, today. Creating a support case now with logs.
-----------------------
Chris Childerhose
Veeam Vanguard / Veeam Legend / Veeam Ceritified Architect / VMCE
vExpert / VCAP-DCA / VCP8 / MCITP
Personal blog: https://just-virtualization.tech
Twitter: @cchilderhose
Post Reply

Who is online

Users browsing this forum: Amazon [Bot], Bing [Bot] and 8 guests