Major Issues After Upgrading to Veeam V13: Port 443 Conflict

[david.domask]

Hi Sylvain, welcome to the fourms.

Thank you for your request -- as noted in the above post by Dima P., the request is under consideration.

[TDMPro2K]

I would also like to be able to change the port... put me on that list requesting this.

[Dima P.]

Hello folks,

The functionality to adjust the HTTPS (443) port for Windows installations is planned. Stay tuned, and thank you for all the feedback!

[hts-gregglanger]

We have a Veeam Backup Enterprise Manager that connects to several Veeam B&R servers at our remote sites and child companies.

As we’ve been upgrading to V13, the requirement to use HTTPS to connect to the VBR server is causing endless issues. Most of these sites are smaller, and only have one external IP that’s used for something user-facing, such as client VPN. (You know, because default ports are good for end users that wouldn’t know how to specify them.)

V12 used Veeam-specific custom ports that we could forward to the VBR servers and there was no issue whatsoever, but the upgrade to V13 has ruined this.

It is necessary to be able to specify a custom port for BEM to collect data from VBR servers. We’re not pointing a web browser at this, and backup software is an ideal place for knowledgeable IT staff to use and document custom ports, or even just a single nonstandard port that Veeam uses by default (like is used to with 9392).

I don’t know who decided it was a good idea to use the single most commonly used port for everything else and make that a requirement for some background communication between a BEM and VBR server. Can I bill Veeam for the multiple sites that now need a second external IP just to monitor backups, because of this change?

Before anyone mentions it: Support instructed me to post here because they wanted to ignore my support ticket instead of help. Not sure what good it’ll do.

[hts-gregglanger]

Hi, Niko. Yes we plan to allow this in the future if there's big demand.

Generally we do not expect the backup server to be shared with 3rd party apps as that commonly leads to unpredictable behavior. And especially we don't expect there would be 3rd party apps accepting incoming connections, as this is the recipe for security breaches resulting in complete take over of the backup server, which as you know contains keys to the entire production environment. Therefore, it's considered a very bad deployment practice.

Thanks

Please consider these responses "big demand" to fix the thing you needlessly broke.

[david.domask]

@hts-gregglanger

Please see the post above your posts (I merged the post from your other topic into this topic)

As DimaP told, this functionality is planned.

[wbauer]

Hi Developers of VBR,

Yes that's worked for the Veeam conflict but I've also had to remove our backup ADFS endpoint since that can't have it's port reassigned. Most of our SMB customers using ADFS don't have a backup endpoint and therefore can't upgrade to V13 until the B&R port can be changed.

This is not working for us. We are using VBR on our Windows Server 2022 Essentials. As we are a small company we can't afford running several servers. This Essentials license does allow only a single domain server setup. So we are running our public Web Server with IIS. Of course you can change the port 443 in IIS but this makes no sense at all, as internet users need to access to our webserver via HTTPS and so port 443 is mandatory. On the other hand we want to stick with VBR as we want to make use of the GFS backup scheme of VBR.

For this reason we can't upgrade to V13 until you add an option to VBR V13 to change the port or you are using an other internal port similar to V12.

Willi

[david.domask]

Hi Willi, welcome to the forums.

Your feedback is understood, please see Dima's post here we plan to allow customization of the port in an upcoming release.