V13 appliance update repo

[jgosnell56]

Hi All,
I am testing a new deployment of 13.0.1.1071. We are in an air-gapped classified environment so I setup a clone of the "https://repository.veeam.com/vsa" repo. I have it being hosted via IIS with the exact directory structure needed. We are running into GPG verification issues though. I have manually updated the GPG key on the appliance by following KB4834 but that did not help any. Can I disable GPG verification within the VSA?

[david.domask]

Hi jgosnell56,

I'm not aware of a means to disable the verification; the KB article must work here, and if you're having technical issues, please open a Support Case as noted when creating a topic. I understand that this is a classified environment, but it's still best to discuss the technical issues with Veeam Support to review why the solution from the KB article did not work.

Please share your case number once created, thanks!

[jgosnell56]

Case #08093172

[jgosnell56]

I was able to figure this out. I performed a new repo clone and transferred everything over but was still getting the 404 error on the .asc and .key files. I could open them fine directly from the Windows server hosting the IIS instance. Digging deeper, I realized that IIS did not have a MIME entry for those file types. I manually added an entry for each extension with type set to text/plain. Now I am seeing an issue where filenames have been changed when I clone the repo so I had to modify my clone script. there are several Kernel packages with "+" in the filename, the was I was cloning prior to my script change was changing the "+" to "%2B" in the filename. That was causing the update to fail due to not being able to download the package.