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

Resolving Port 443 Conflicts in Veeam Backup & Replication In modern data centers, port 443 (HTTPS) is a critical gateway for web services, APIs, and secure communications. For 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, the Veeam upgrade will be blocked, or the services will fail to start. Identifying the Conflicting Application

Before resolving the conflict, you must identify which process is currently holding the port.

Command Line: Open a command prompt as an administrator and run:netstat -ano | findstr :443

Locate the PID: The right-most column of the output is the Process ID (PID).

Task Manager: Open Task Manager, go to the Details tab, and match the PID to find the application name.

PowerShell Alternative: Use Get-NetTCPConnection -LocalPort 443 to directly see the OwningProcess. Common Conflicting Services

The most frequent culprits for port 443 occupation on a Windows server include:

Major Issues After Upgrading to Veeam V13: Port 443 Conflict

Let's dive deep into the issue of port 443 being occupied by another application when trying to use it for Veeam Backup replication. Resolving Port 443 Conflicts in Veeam Backup &

Understanding the Issue

Veeam Backup & Replication uses various ports for communication between components, including the Veeam Backup Server, Proxy Servers, and Repository Servers. One of these ports is TCP 443, which is typically used for HTTPS traffic.

When you try to configure Veeam Backup replication, you may encounter an error message indicating that port 443 is already in use by another application. This can be frustrating, especially if you're not aware of what application is using the port.

Common Causes of Port 443 Occupation

Here are some common causes of port 443 being occupied:

1. Other backup or replication software: Another backup or replication software might be using port 443 for its own communication. Examples include other backup solutions like Commvault, NetBackup, or Data Protection Manager.
2. Web servers or IIS: If you have a web server or IIS (Internet Information Services) installed on the same machine as your Veeam Backup Server, it may be using port 443 for HTTPS traffic.
3. SSL/TLS certificates or services: Services like Certificate Authority (CA) servers or SSL/TLS certificate management tools might use port 443 for certificate-related communication.
4. Other applications or services: Any other application or service that uses HTTPS or SSL/TLS might be occupying port 443.

How to Identify the Occupying Application

To identify which application is using port 443, follow these steps:

On Windows:

1. Open a Command Prompt as an administrator.
2. Run the command: netstat -anop | findstr 443
3. This will list all processes using port 443. Look for the PID (Process ID) of the process using the port.

On Linux:

1. Open a Terminal.
2. Run the command: netstat -tlnp | grep 443
3. This will list all processes using port 443. Look for the PID (Process ID) of the process using the port.

Once you've identified the occupying application, you can:

1. Stop the occupying application: If possible, stop the application or service using port 443.
2. Change the occupying application's port: If possible, change the port used by the occupying application to a different port.
3. Configure Veeam Backup to use a different port: You can configure Veeam Backup to use a different port for replication. To do this, go to Veeam Backup & Replication > Settings > Network > Ports, and change the Port value for Replication to a different port (e.g., 4433).

Additional Considerations

When changing ports, consider the following:

• Ensure that any firewalls or network access control lists (ACLs) are updated to allow traffic on the new port.
• Verify that all Veeam Backup components (e.g., Backup Server, Proxy Servers, Repository Servers) are configured to use the new port.
• If you're using a load balancer or reverse proxy, you may need to update its configuration to route traffic to the new port.

By following these steps and considerations, you should be able to resolve the issue of port 443 being occupied by another application when trying to use it for Veeam Backup replication.

2. Root Cause Analysis

Port 443 is the standard HTTPS port. Common applications that conflict with Veeam include:

| Application / Service | Typical Context | |----------------------|------------------| | IIS (Internet Information Services) | Default web server on Windows; may host other websites or management consoles. | | Microsoft Exchange Server | Uses port 443 for Outlook Web Access (OWA) and Exchange Admin Center. | | Skype for Business / Teams (on-prem components) | Uses port 443 for web conferencing and mobility services. | | Apache / Nginx | Third-party web servers running on same Windows VBR server. | | VMware vCenter Server (embedded) | If Veeam is installed on a vCenter Server (not recommended). | | SQL Server Reporting Services (SSRS) | Uses port 443 for report manager. | | Third-party antivirus / proxy services | Some inject a local HTTPS inspection proxy. |

A Quick Word on Best Practices

• Avoid port conflicts from the start: Don’t install Veeam on a machine already running a web server, Skype, or SQL Server with Reporting Services.
• Use dedicated servers for Veeam backup components.
• Document your ports – Especially if you’re running multiple data protection tools in a lab or production environment.

Step 5: Check for Stale Veeam Services

If you recently uninstalled Veeam or had a failed upgrade, some services may linger. Other backup or replication software : Another backup

Open services.msc and look for:

• Veeam Backup Service
• Veeam REST API Service
• Veeam Cloud Connect Service

If they exist and are stuck in "Starting" or "Stopped" state, manually stop them and set to Disabled. Then reboot before re-running the Veeam installer.

Step 3: Handling IIS (Default Web Site)

If w3wp.exe or inetinfo.exe is the offender, IIS is running. You have three choices:

Option A (Recommended for Veeam only): Change IIS to another port.

1. Open IIS Manager.
2. Select Sites → Default Web Site.
3. In the right-hand Actions pane, click Bindings.
4. Select the https entry on Port 443 and click Edit.
5. Change the port to 8443 (or any unused port >1024).
6. Restart IIS: iisreset

Option B: Stop and disable IIS (if not needed).

• In Server Manager → Manage → Remove Roles and Features. Uncheck Web Server (IIS).

Option C: Stop IIS temporarily for Veeam to install, then re-bind later.

• iisreset /stop → install Veeam → iisreset /start (but you’ll need to change bindings eventually).

What If You Cannot Free Port 443? (The Alternative)

In some environments, Port 443 is a business-critical endpoint for a public-facing web server or reverse proxy. Reconfiguring that application may be impossible.

Veeam allows you to change its default ports (with caveats). How to Identify the Occupying Application To identify

Step 4: Restart & Retry

After freeing port 443:

• Restart the Veeam Backup Service (or reboot if unsure).
• Rerun the Veeam installation or configuration wizard.