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

This error occurs when another service is using TCP port 443 Veeam Backup & Replication (VBR) v13 and newer requires for its Web Service/API Gateway

. In these versions, port 443 is often hardcoded during the installation or upgrade process, and there is no official, supported way to change it for the Web Service component. Veeam Community Resource Hub Step 1: Identify the Conflicting Application

To fix this, you must first find which process is currently "squatting" on port 443. Open PowerShell or Command Prompt as Administrator. Run the following command to find the Process ID (PID) using port 443: powershell netstat -aon | findstr : Use code with caution. Copied to clipboard Identify the process name using the PID found in the last column: powershell -Id Use code with caution. Copied to clipboard Stack Overflow Common culprits for this conflict include: Hyper-V Replication: Often uses 443 by default for HTTPS replication. IIS (Internet Information Services): Web servers hosted on the same machine. Third-party monitoring or time-tracking software: Examples include applications like Timemaster. System Process (PID 4):

This usually indicates a Windows service like HTTP.sys is holding the port. Step 2: Resolve the Conflict

Veeam requires port 443 to be free during the upgrade or installation. You have three main options: Option A: Reconfigure the Other Application (Recommended)

If the conflicting application allows port changes, move it to a different port (e.g., 444 or 8443).

Major Issues After Upgrading to Veeam V13: Port 443 Conflict

Required Port 443 for Veeam Backup Replication is Occupied by Another Application: A Comprehensive Guide

Veeam Backup & Replication is a popular data backup and disaster recovery solution used by many organizations to protect their critical data. One of the key requirements for Veeam Backup & Replication to function properly is that it needs to communicate over specific ports, with port 443 being one of them. However, what happens when the required port 443 for Veeam Backup replication is occupied by another application? In this article, we will explore the issues that arise when port 443 is occupied, and provide a step-by-step guide on how to resolve this common problem. This error occurs when another service is using

Understanding Port 443 and Veeam Backup & Replication

Port 443 is the default port used for HTTPS (Hypertext Transfer Protocol Secure) communication. Veeam Backup & Replication uses this port to establish a secure connection between the backup server and the vCenter server or ESXi hosts for replication and backup operations. When Veeam Backup & Replication is configured to use port 443, it attempts to establish a secure connection to the target server. However, if another application is using port 443, the Veeam Backup & Replication job will fail.

Causes of Port 443 Occupation

There are several reasons why port 443 may be occupied by another application:

1. Multiple HTTPS applications: If there are multiple applications running on the same server that require HTTPS communication, they may be using port 443, causing a conflict with Veeam Backup & Replication.
2. Web server configurations: A web server like IIS or Apache may be configured to use port 443 for HTTPS communication, blocking Veeam Backup & Replication from using it.
3. Other backup or replication tools: Other backup or replication tools may be using port 443 for their own communication, causing a conflict with Veeam Backup & Replication.
4. Incorrect Veeam Backup & Replication configuration: If Veeam Backup & Replication is not configured correctly, it may attempt to use a port that is already occupied by another application.

Symptoms of Port 443 Occupation

When port 443 is occupied by another application, Veeam Backup & Replication may exhibit the following symptoms:

1. Failed backup or replication jobs: Veeam Backup & Replication jobs may fail with error messages indicating a connection issue.
2. Timeout errors: Backup or replication jobs may timeout, indicating that the connection to the target server could not be established.
3. SSL/TLS errors: Errors related to SSL/TLS certificates or secure connections may occur.

Resolving Port 443 Occupation

To resolve the issue of port 443 being occupied by another application, follow these steps: Multiple HTTPS applications : If there are multiple

Step 1: Identify the Occupying Application

1. Open a command prompt or terminal on the server where Veeam Backup & Replication is installed.
2. Run the command netstat -anop | findstr 443 (on Windows) or lsof -i :443 (on Linux) to identify the application using port 443.
3. Note down the process ID (PID) and name of the occupying application.

Step 2: Change the Occupying Application's Port

1. If possible, change the occupying application's port to a different one. For example, if a web server is using port 443, you can change its configuration to use a different port, such as 444.
2. Restart the occupying application for the changes to take effect.

Step 3: Configure Veeam Backup & Replication to Use a Different Port

1. Open the Veeam Backup & Replication console and navigate to Backup Infrastructure > vCenters.
2. Select the vCenter server or ESXi host and click Properties.
3. In the Properties window, navigate to the Advanced tab.
4. In the Advanced tab, click Add and enter the new port number you want to use instead of 443.
5. Click OK to save the changes.

Step 4: Verify Veeam Backup & Replication Connectivity

1. Test the connectivity between the Veeam Backup & Replication server and the vCenter server or ESXi host using the new port.
2. Verify that backup and replication jobs are successful.

Alternative Solutions

If changing the occupying application's port or configuring Veeam Backup & Replication to use a different port is not feasible, consider the following alternative solutions:

1. Use a port redirector: Configure a port redirector to forward traffic from port 443 to a different port used by Veeam Backup & Replication.
2. Disable the occupying application: If the occupying application is not critical, consider disabling it or stopping its service.

Conclusion

When the required port 443 for Veeam Backup replication is occupied by another application, it can cause significant disruptions to your backup and replication operations. By understanding the causes of port 443 occupation and following the steps outlined in this article, you can resolve the issue and ensure that your Veeam Backup & Replication jobs run smoothly. Additionally, consider implementing monitoring and logging to detect potential port conflicts and other issues before they impact your critical backup and replication operations. Symptoms of Port 443 Occupation When port 443

Preventative Measures: Avoiding Future Conflicts

1. Install Veeam on a dedicated server – Do not stack Veeam on top of an existing IIS or RD Gateway server.
2. Use a standard port assignment policy – Document that port 443 belongs to Veeam in your backup environment.
3. During OS provisioning: Use Disable-NetFirewallRule and pre-configure HTTP.SYS reservations to ignore Veeam’s range.
4. Leverage Veeam’s ‘Ports’ documentation – Veeam has a full list (e.g., 135, 445, 2500-3300, 6160) to avoid accidental overlaps.

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:

1. Reconfigure the other app to use a different port (e.g., 8443, 9443).
2. Change Veeam’s port (less common but possible for some components like the Veeam WAN Accelerator or Guest Interaction Proxy). In Veeam, edit the component’s properties under Backup Infrastructure.

Step 1: Identify the Process Using Port 443

Do not guess. Use built-in Windows tools to get the definitive Process ID (PID).

Method A: Using Command Prompt (as Administrator)

netstat -aon | findstr :443

You will see output similar to: TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 4488

The number 4488 is the PID. Now, find the process name:

tasklist | findstr 4488

Method B: Using PowerShell (as Administrator)

Get-NetTCPConnection -LocalPort 443 | Select-Object -Property LocalPort, State, OwningProcess
Get-Process -Id (Get-NetTCPConnection -LocalPort 443).OwningProcess

What to look for:

• System (PID 4) – Usually indicates HTTP.SYS kernel driver is reserving the port. This is often due to IIS or SSRS.
• w3wp.exe – IIS worker process.
• sqlservr.exe – SQL Server (if SSRS is enabled).
• veeam* – A stale Veeam process.

Before you begin (precautions)

• Schedule a maintenance window or perform during low-impact hours.
• Back up Veeam configuration (Configuration Backup in Veeam console).
• Note services that will be restarted (Veeam services, IIS, or conflicting app).
• Have administrative access on the Veeam server.

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 6: Edge Cases – Docker, Remote Desktop Gateway, Antivirus

• Docker: Run docker run --rm --net=host alpine netstat -tulpn (WSL/Windows containers). Stop Docker service via services.msc or net stop docker.
• RD Gateway: Open Server Manager → Remote Desktop Services → RD Gateway Manager. Change the SSL port to 4430.
• Antivirus (e.g., McAfee Web Gateway): Open your AV console, locate HTTPS or Web Control features, and disable transparent SSL proxying for the Veeam server IP.

Symptoms

• Veeam services fail to start or report binding errors referencing port 443.
• Veeam Backup & Replication Console or Web UI not reachable.
• Errors in Veeam logs mentioning “address already in use”, “port already bound”, or HTTP/HTTPS listen failure.
• Replication or backup jobs fail to connect to remote components.