I've already created a supportcase on this issue: #08138893
Im in the middle of setting a local mirror for veeam updates.
We have a VSA, 4 VIA's and 2 VHRs.
It works great on the VSA and 4 VIAs, but on the two VHRs, the job fails with: "Failed to connect to Veeam updater service. "
And if I access the Web host management Console of the VHRs, theres a error stading:
"Product Updates require an active maintenance contract. Please consider joining this appliance to your Veeam backup and replication infrastructure and apply the license"
The thing is, we have an valid license on the VSA, and both VHRs are connected to the VSA/VBR.
-
EviLin
- Enthusiast
- Posts: 44
- Liked: 7 times
- Joined: Apr 28, 2025 7:37 pm
- Contact:
-
david.domask
- Product Manager
- Posts: 3717
- Liked: 905 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: [V13] - VBR cant connect to VHRs V13 Veeam updater service
Hi EvilLin,
Thanks for sharing the case number, but please continue with Support and wait for the conclusion as per the forum rules. If there are questions after the conclusion to the support case, then a topic with the case id is appropriate
The situation does not seem expected, so research by Veeam Support will be required, unclear just from the above why you're getting the "no license" error.
Thanks for sharing the case number, but please continue with Support and wait for the conclusion as per the forum rules. If there are questions after the conclusion to the support case, then a topic with the case id is appropriate
The situation does not seem expected, so research by Veeam Support will be required, unclear just from the above why you're getting the "no license" error.
David Domask | Product Management: Principal Analyst
-
TimoB
- Novice
- Posts: 7
- Liked: 1 time
- Joined: Jul 04, 2018 8:11 am
- Contact:
Re: [V13] - VBR cant connect to VHRs V13 Veeam updater service
Hi EviLin,
I just stumbled across a similar issue in an environment, where both components were in different nets and separated by a firewall.
In my case, the VBR server was unable to reach the VIA via port 443.
It's a shot in the dark, and surely Veeam support will be able to solve that, but maybe it's the same issue.
I just stumbled across a similar issue in an environment, where both components were in different nets and separated by a firewall.
In my case, the VBR server was unable to reach the VIA via port 443.
It's a shot in the dark, and surely Veeam support will be able to solve that, but maybe it's the same issue.
Who is online
Users browsing this forum: Google [Bot] and 142 guests