Comprehensive data protection for all workloads
Post Reply
Stabz
Expert
Posts: 166
Liked: 20 times
Joined: Apr 07, 2017 7:40 am
Full Name: Philippe DUPUIS
Contact:

[V13] Hardened Repository update issue #07993991

Post by Stabz »

Hi folks,

I figured out an issue since I upgraded a customer to VBR v13. I'm unable to upgrade our Hardened Repository server during the "Component Update" phase, with the error: "Unable to deploy the Veeam Deployer service due to SSH credentials not specified."

To fix this, I had to navigate to Backup Infrastructure, select the server, and click on "Edit Server" to re-enter the single-use credentials. The communication then works, but I get the following message:

Failed: Installing Installer service — Error: execution timeout...

I opened a ticket (#07993991). The problem is that my Linux server has no HTTPS internet access. Port 443 must be open to reach RHEL's repositories and check for dependencies when installing applications.

Logs from the dnf file:
2026-02-18T12:04:24+0100 DDEBUG Base command: install
2026-02-18T12:04:24+0100 DDEBUG Extra commands: ['--assumeyes', '--errorlevel=0', 'install', '/tmp/veeamdeployment-13.0.1.1071-1.x86_64.rpm', '--setopt=skip_if_unavailable=true']
2026-02-18T12:04:24+0100 DEBUG User-Agent: constructed: 'libdnf (Rocky Linux 9.5; generic; Linux.x86_64)'
2026-02-18T12:04:24+0100 DEBUG countme: no event for epel: window already counted
2026-02-18T12:04:54+0100 DEBUG error: Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metal ... =pub/rocky [Failed to connect to mirrors.fedoraproject.org port 443: Connection timed out]
2026-02-18T12:05:24+0100 DEBUG error: Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metal ... =pub/rocky [Failed to connect to mirrors.fedoraproject.org port 443: Connection timed out]
2026-02-18T12:05:54+0100 DEBUG error: Curl error (28): Timeout was reached for https://mirrors.fedoraproject.org/metal ... =pub/rocky [Failed to connect to mirrors.fedoraproject.org port 443: Connection timed out]
2026-02-18T12:06:07+0100 INFO --- logging initialized ---
I didn't see any mention of this in the prerequisites. If we can't open the repository to the internet, this could be problematic.
I m looking to find a solution
vnikiforov
Product Manager
Posts: 40
Liked: 12 times
Joined: Aug 17, 2022 5:03 am
Full Name: Vladimir Nikiforov
Location: Romania
Contact:

Re: [V13] Hardened Repository update issue #07993991

Post by vnikiforov »

Hello, Philippe,

From the case, I can see that you were able to find a solution to get the update to go through. Glad to hear it.
What was the solution? Disable the base repositories manually to get the installation through? Please let me know.

Allow me some time to check internally on this behavior, and I will update with more information
---
BR,
Vladimir
Veeam Software
Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 18 guests