Veeam B&R 13 Change Web Service Port 443

Are you referring to Enterprise Manager and not VBR?  The port change is done in IIS and then you need to update the configurations for any URLs.  This can be tricky as you need to find the configuration files.

I would contact support get them to assist you with this.  Too bad the other app uses the same port - is is not easier to change that one?

No, I’m talking about the new VBR v13.  It now has a service called ‘Veeam Web Service’ which requires port 443 to be available during the install and we see no way to change this after the upgrade.  This is an issue for small clients with a single server that isn’t virtualized, that need 443 for an existing service or app.

Hi ​@luke7562, from architectural and best-practice standpoint. Is running additional services on the same machine as Veeam Backup & Replication not a bad setup?

> So when we attempt to upgrade from v12 to v13, it won’t install since 443 is being used

In response to your question, this behavior is expected because the installer blocks the upgrade when a conflicting service is using the required port. I recommend stopping the conflicting service and then performing the upgrade. Based on past experience with other systems, I believe that after the upgrade, you can change the port.

To reproduce your error, I suggest spinning up a VM, installing VBR along with another service that uses the same port, stopping the conflicting service, and performing the upgrade. After the upgrade, verify whether you can change the port. Once this works, you can proceed with your production environment. Don’t forget to share the steps with the community once this is done.
 

Note: I am yet to perform this upgrade. This information is provided “as is” without warranty of any kind. You are responsible for your own actions as I am not veeam support!

Gotcha.  Yeah try stopping the app service, do the upgrade to VBR and then try changing the port to see.  Again I would suggest a support ticket for this to get them to assist as I am sure there is a way to change the port.

Yes, this would technically be considered a “bad setup” and not best practice. However, we’re dealing with clients who have only a handful of employees and can barely justify the cost of a dedicated server versus a simple workgroup. In these cases, the typical setup is often a single physical server running Windows, handling Active Directory, file sharing, and a required software package that already uses port 443—which, in some instances, cannot be changed.

To replicate the issue, I’ve spun up a VM and tested the upgrade from v12 where port 443 was already in use. I was able to temporarily disable the service using 443 and successfully complete the upgrade to v13. Unfortunately, after the upgrade, I haven’t found a way to configure Veeam to use a different port. For some clients, we can reconfigure the conflicting service to another port, but there are cases where that won’t be possible.

I’d prefer not to leave these clients on v12 long-term, and moving them to the basic Windows Agent isn’t an ideal solution either.

And yes, I will be contacting support to see if they have a solution.

Contact support and open a ticket to get them to assist you.  I am sure they can explain how to change the port.

I have the same problem, that I can’t update, but there is noch running service on 443, it’s blocked by system prozess PID 4, so I can’t stop or change it.

Contact support and see if they can assist. Easiest way forward.

Thank you, ​@AdmiralAR1 for reverting. 

WOW so system requirements are really going to have to be checked before installing so no one runs in to this issue.  I guess that is why they recommend installing on its own machine or using the VSA now.

Thanks for sharing the response from support.

I’m not even using 443, sometime 443 is just blocked by PID 4

I had this issue, its usually due to a Windows component like RRAS or ADFS. These use the http.sys driver to extract relevant incoming 443 traffic, which is driven by the SYSTEM process (PID 4).

It’s quote frustrating, we have a VM dedicated specifically for Veeam services (365 Backup, B&R Cloud Connect and VSPC) and now that isn’t even compatible because VSPC is on 443. We also deal primarily with small customers who may not have the server resources to spin up a whole extra VM because we can no longer use B&R on their existing VMs due to port conflicts.

Same here, we have two small customers that need to use the port 443 and they are blocked due to this dumb decision from Veeam to use the port 443 with no way to change it ...

Same issue. This really is unacceptable.

Best place to put this is in the Forums so Product Managers see it or check if there is already a topic.