The Veeam Updater is still required to be used in order to keep the appliance up to date with various security related updates that come out regularly. (To not use the Updater and just wait for the next appliance update is a security risk that is unacceptable.) I recently had an issue where the bell icon was telling me that there were updates that needed to be installed, and when I clicked on that bell I was taken to the Veeam Updater and was presented with an error that the appliance "Cannot access the Veeam Repository." (I opened case #07743940 and have since worked around this, so I'm putting this in as a result of that case for a feature request.)
What support found was that there was an issue disclosed in the logs about certificate issues on the repos in the appliance:
Based on this, their recommendation was to log into the system using SSH and running apt-get commands in order to update things and now everything is working fine, until it happens again.2025-06-22 16:37:44.1600 00052 [642] WARN | [Shell]: [null]: System.InvalidOperationException: Process 'apt-get -y update -o Acquire::http::Timeout=15 -o Acquire::Retries=2 -o APT::Update::Error-Mode=any -o APT::Get::List-Cleanup=0' has finished with exit code 100, error: W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://nginx.org/packages/ubuntu jammy InRelease: The following signatures were invalid: EXPKEYSIG ABF5BD827BD9BF62 nginx signing key <signing-key@nginx.com>
My feature request is to fix the Veeam Updater so that it can take corrective actions like this on its own, or provide me with a checkbox when it gets an error that it can fix (like this one), and have it try to fix it directly. Forcing me to log into the server with SSH, when that isn't something I do on a regular basis at all, is a bit onerous, not to mention I might not have the ability to log into the server directly due to cloud configurations and permissions not allowing incoming SSH or whatever. Since VBAz Web UI was working, it clearly had access to the system, and it has the right permissions in order to take these actions, so not sure why you're forcing us to have to do something outside of that or, even worse, trying to explain to the cloud system administrators that do have access, which commands to run and then wait for them to run them and hope things work properly at the end.
Thanks.