Required Port 443 For Veeam Backup Replication Is Occupied By Another Application Link

Troubleshooting Veeam: "Port 443 is Occupied by Another Application"

If you are installing or upgrading Veeam Backup & Replication (VBR), encountering the error "Required port 443 for Veeam Backup & Replication is occupied by another application" is a common, albeit frustrating, roadblock.

Port 443 is the standard port for HTTPS traffic. Because it is the default secure port for the web, many applications (IIS, Skype for Business, VMware Update Manager, and various web servers) fight for control over it. Veeam requires this port for its internal web server to communicate with the console, mount servers, and manage the backup infrastructure. Troubleshooting Veeam: "Port 443 is Occupied by Another

This article explores how to identify the culprit and resolve the conflict without compromising your network security. Example output: TCP 0

3.1 Identify the Conflicting Process

netstat -ano | findstr :443

Example output:

TCP    0.0.0.0:443           0.0.0.0:0              LISTENING       1234

The number 1234 is the Process ID (PID). Test Veeam functionality:

Why Does Veeam Need Port 443?

Before diving into solutions, it is critical to understand why Veeam insists on Port 443. Veeam Backup & Replication uses Port 443 for several key functions:

1. Veeam Backup Service (vssvc): The main Veeam service uses HTTPS for secure communication between the backup server, proxies, repositories, and guest interaction proxies.
2. Veeam REST API Service: Modern Veeam versions (v10 and later) expose a powerful RESTful API over HTTPS. This service binds to Port 443 by default.
3. Enterprise Manager Integration: If your Veeam server is part of an Enterprise Manager deployment, Port 443 is used for web-based reporting and management.
4. Cloud Connect: For service providers, Port 443 is the gateway for tenant backup traffic.

If another application is squatting on Port 443, Veeam cannot start its core listening services, leading to installation rollbacks or failed service startups.

Step 4 — Restart services and verify

1. Restart affected services or the server if needed.
   • Windows example:

     Restart-Service W3SVC
     Restart-Service VeeamBackupSvc
     

2. Verify port is now free or bound by the intended service:

   netstat -ano | findstr :443
   

3. Test Veeam functionality:
   • Open Veeam Backup & Replication Console / Web UI.
   • Run a test job or connect to remote components.