[V13] Question/Request port reg.?

[EviLin]

Hello,

Im really missing a overview of what network ports that needs to be open between the different products, especially regarding JeOS (VSA and VIA).

I've had an support case regarding I Could'nt update our Veeam Hardend repo,for some days, and all the issues was regarding missing firewall ports to be open between our VBR windows server and the VHR, and VHR and the repository.veeam.com, both things missing in your current port overview.

[pybfr]

Hello,
What were the port missing from:
https://helpcenter.veeam.com/docs/vbr/u ... kup-server
https://helpcenter.veeam.com/docs/vbr/u ... er=13#repo

Nevertheless, there is a "send feedback" link at the bottom of the page where you can pass along gaps and typo to the tech writers team

[EviLin]

This is the case number: # 07904752

We could'nt update VHR (VIA 13), because in our firewall the only port open from VHR to VBR was:
2500 to 3300

And it also needs 443 from VHR to VBR.

Also I dont see anywhere that the VHR needs access to repository.veeam.com , only that the VBR server needs that access.
I thought in V13, that all access to repository.veeam.com was from the VBR server only, because then VBR would distribute the updates to the managed servers VIA/VHR etc.
But the VHR still needs access to repository.veeam.com

[Gostev]

That is definitely not the case, VSA does not host a software repository. You will see that in VIA software repository settings which just like VSA also point to the veeam.com software repository by default.

I'm not sure if VSA will ever host a software repository as it will increase attack surface. Veeam Backup Enterprise Manager seems like a good candidate to become the only infrastructure component with Internet access and hosting software repositories, but we're still considering.

[EviLin]

Ohh okay.

I was just under the impression that VSA would function as an 'bridge'/distribution of the updates. Sorry for that then.

[Gostev]

It does act as a bridge/distribution for automatic update settings, which particularly includes the software repository to use. But then all components go to that repository directly.