Veeam Update URL´s

[Nikolauspflege]

Hi,

i installed a new veeam infrastructure appliance to use it as hardened repo for my VBR server.
But when adding the VIA to VBR everything is successfull besides the update inventory/check.

I have a firewall rule in place that allows my veeam servers (VBR and VIA) to connect to the following URL´s via 443:
- dev.veeeam.com
- repository.veeam.com
- vbrad.butler.veeam.com
- vbrce.butler.veeam.com
- autolk.veeam.com

When i change this firewall rule to allow any URL, the update check succeeds.
I have opened a ticket (#07936483) an support has also told me, that repository.veeam.com should be sufficient. But our firewall still blocks connections to external IP adresses.

Wich URL´s have you guys allowed?

Best regards

Hannes

[Mildur]

Hi Nikolauspflege,

These URL endpoints are correct (I assume "dev.veeeam.com" is a typo and you meant "dev.veeam.com") for the Backup Server.
The Infrastructure Appliance (Hardened Repository) only needs internet access to repository.veeam.com.

Please also make sure that the Infrastructure Appliance can communicate with the Backup Server on port 443, and vice versa — the Backup Server must be able to reach the Infrastructure Appliance on port 443. Otherwise, the appliance will not be able to retrieve download tasks from the Backup Server.

All required ports are listed in our documentation.

Best,
Fabian

PS: I replaced your contract ID #03 with the actual case number #07

[Nikolauspflege]

Thank you. The VBR server and trhe appliance are in the same network/subnet so there is no firewall in between.
We changed the firewall rule to any again and were able to add the appliance.
I then removed it once again and we set the rule to repository.veeam.com and this time it also worked.
Maybe bug in the firewall rule, maybe magic, maybe the appliance installed the update while the rule was set to any and will fail once there is a new update coming.

I will soon be able to test it again with a seperate appliance.

Thanks for your input.

Regards

[DaStivi]

in the docs are a couple more URLs:

- dev.veeam.com
- repository.veeam.com
- vbrad.butler.veeam.com
- vbrce.butler.veeam.com
- vbr.butler.veeam.com
- autolk.veeam.com
- rest-ai.veeam.com
- avupdate.veeam.com

[Mildur]

Hi Stephan,

The Veeam Infrastructure Appliance itself only needs access to the update repository (repository.veeam.com).
The other URLs you have mentioned must be reachable by the Backup Server or other specific roles, but not by the Infrastructure Appliance when updating the operating system.

Best,
Fabian

[FreddyN]

Hi Guys

Anything new on this topic? I have a similar "problem".
The firewall blocks severall connections to cloudfare.net as soon as we start checking for updates.

/Freddy

[Mildur]

According to the case notes, the issue was likely caused by a firewall bug.
The firewall was blocking access to the URLs documented in our Help Center, even though the exclusions were configured correctly.

If you’re experiencing a similar problem, please share your own case number. We cannot investigate such issues through a forum topic.

Thank you,
Fabian