Required Port 443 For Veeam Backup Replication Is Occupied By Another Application Link May 2026
In Veeam Backup & Replication (VBR) v13, Port 443 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
Scenario 1: IIS (Internet Information Services) is using Port 443
If System (PID 4) is holding the port, it is likely IIS. In Veeam Backup & Replication (VBR) v13, Port
Troubleshooting tips
- Check Veeam logs (C:\ProgramData\Veeam\Backup) for precise error messages.
- If netsh shows HTTPS reservations, inspect:
netsh http show sslcert netsh http show urlacl - Use Process Explorer to inspect which service has the handle if PID maps to svchost.exe — look at service name(s).
- If a service uses HTTP.sys and appears as System or svchost, use:
to map the service.sc queryex <serviceName> - For Docker on Windows, check Hyper-V/NAT port mappings.
netstat -ano | findstr :443
Veeam Backup & Replication v13 is a hardcoded requirement for the Veeam Web Service/API Gateway Use Process Explorer to inspect which service has
Step 3: Change the Conflicting Service’s Port
If you can’t stop the other application (e.g., it’s another critical backup tool), you have two options: it’s another critical backup tool)
Update the replica settings for each VM to match this new port Windows Remote Management (WinRM)