Proceed through the wizard until you reach the step.
Veeam Backup & Replication requires TCP Port 443 specifically for its . This service acts as the secure communication channel (using HTTPS) between the Veeam Backup Server, Backup Proxies, Backup Repositories, and Managed Servers (vCenter/ESXi/Hyper-V).
Older versions historically utilized ports 80 and 443 as fallbacks for incoming connections.
Open the , type cmd , right-click Command Prompt , and select Run as administrator . Type the following command and press Enter : netstat -ano | findstr :443 Use code with caution.
: If you are using the Console (formerly Availability Console) rather than VBR itself, the port be changed via IIS Manager > Edit Bindings Infrastructure Segregation Proceed through the wizard until you reach the step
Once the conflict is cleared, restart the stopped Veeam services to restore normalcy. Press Win + R , type services.msc , and press Enter. Locate all services starting with .
Some security solutions (e.g., McAfee Web Gateway, Symantec Endpoint Protection’s web component) or legacy backup agents run a local HTTPS listener for management.
Before troubleshooting, it helps to understand exactly why Veeam needs this specific port. The role of port 443 varies across different Veeam versions and components:
for the Veeam Web Service/API Gateway. This requirement is strictly enforced by the installer's compatibility check, and there is currently no supported way to change this port within Veeam or bypass the check. Identifying the Conflict Older versions historically utilized ports 80 and 443
Once you know what application is using the port, choose one of the following methods to resolve the conflict. Method A: Stop or Disable the Conflicting Service
to change its own internal web service port during installation, you must move the application: For Hyper-V: Hyper-V Settings Replication Configuration Change the port from to another available port (e.g., Update your individual VM Replication settings to match. IIS Manager (InetMgr.exe) , right-click the conflicting site, and select Edit Bindings Change the HTTPS port from
Scenario 1 — IIS default website bound to 443 blocking Veeam
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 : If you are using the Console (formerly
Troubleshooting "Port 443 Required for Veeam Backup & Replication is Occupied by Another Application"
Veeam Backup & Replication is widely regarded as the gold standard for data protection in virtual, physical, and cloud environments. However, even the most robust platforms can encounter installation or upgrade issues. One of the most frustrating and frequently reported errors during Veeam deployment or service restart is:
: It is used by Veeam Agents to obtain authentication tokens from the Veeam Backup Identity Service Hardcoded Configuration
Resolving the Conflict: Required Port 443 for Veeam Backup & Replication is Occupied by Another Application
This guide provides a comprehensive, step-by-step walkthrough to identify the conflicting application, free up the port, or reconfigure Veeam to use an alternative port. Why Veeam Requires Port 443