In Veeam Backup & Replication (VBR) v13, is a hardcoded requirement for the REST API and Web UI services. If this port is occupied by another application during installation or upgrade, the Veeam services will fail to bind and start. Identifying the Conflicting Application
: Internal services within an organization might be misconfigured to use port 443, causing unexpected conflicts with Veeam Backup Replication. In Veeam Backup & Replication (VBR) v13, is
Started.
| Problem | Quick Fix | | :--- | :--- | | PID 4 (System) / HTTP.SYS reservation | netsh http delete urlacl url=https://+:443/ | | IIS running | Change Default Web Site’s HTTPS binding to 8443 | | SQL SSRS | Change Reporting Services port to 4443 | | RD Gateway | Change SSL port in RD Gateway Manager | | Docker / Containers | Stop docker or com.docker.service | | Antivirus web filter | Disable SSL intercept for the Veeam server IP | | No other option | Change Veeam’s own HttpPort registry key to 8443 | Started
: If the conflicting application is only needed occasionally, stop the service, complete the Veeam v13 upgrade, and then attempt to restart the other service. Note that Veeam v13 services will still fail to start if the port is occupied later. Major Issues After Upgrading to Veeam V13: Port 443 Conflict
Major Issues After Upgrading to Veeam V13: Port 443 Conflict