Local installations of VMware Workstation, Apache, or Nginx often claim port 443 for shared virtual machine management or local web hosting.
If you installed VMware Workstation or vCenter components on the same Windows Server as Veeam, VMware will hijack port 443 for its shared virtual machines service.
Get-NetTCPConnection -LocalPort 443 | Select-Object LocalAddress, LocalPort, OwningProcess, @Name="ProcessName";Expression=(Get-Process -Id $_.OwningProcess).Name Use code with caution. Step 2: Common Culprits and How to Fix Them Local installations of VMware Workstation, Apache, or Nginx
If you cannot change the port of the other application, you can reconfigure Veeam to use a different port for its web UI or API components during installation or via the registry/configuration files.
Major Issues After Upgrading to Veeam V13: Port 443 Conflict Step 2: Common Culprits and How to Fix
Starting with recent versions (v13+), this port is hardcoded for the API Gateway, meaning the installer checks for its availability and fails if another service is listening on it. 1. Identify the Conflicting Application
) to finish the Veeam installation, then re-evaluate the service's port requirements afterward. Do you need help checking if Hyper-V Replication is specifically causing the hold-up on your server? Identify the Conflicting Application ) to finish the
Once you have identified the application holding the port, choose one of the following remediation paths. Option 1: Stop or Uninstall the Conflicting Application
When you install Veeam Backup & Replication (version 10, 11, 12, or later), the installer attempts to bind the to port TCP 443 on the local machine. If any other process has already claimed that port—even if it's just listening and not actively serving traffic—Veeam will refuse to start or install.
If it doesn't exist, you may need to look under the specific service keys:
Resolving Port 443 Conflicts in Veeam Backup & Replication Veeam Backup & Replication relies heavily on port 443 for secure communication. It uses this port to connect with VMware vCenter Servers, ESXi hosts, and cloud repositories. When another application occupies port 443, Veeam services fail to start, backups halt, and infrastructure management becomes impossible.