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

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.

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:

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.
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.
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.
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:

Failed backup or replication jobs: Veeam Backup & Replication jobs may fail with error messages indicating a connection issue.
Timeout errors: Backup or replication jobs may timeout, indicating that the connection to the target server could not be established.
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:

Step 1: Identify the Occupying Application

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

Step 2: Change the Occupying Application's Port

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.
Restart the occupying application for the changes to take effect.

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

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

Step 4: Verify Veeam Backup & Replication Connectivity Required Port 443 for Veeam Backup Replication is

Test the connectivity between the Veeam Backup & Replication server and the vCenter server or ESXi host using the new port.
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:

Use a port redirector: Configure a port redirector to forward traffic from port 443 to a different port used by Veeam Backup & Replication.
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.

Veeam Backup & Replication v13 is a hardcoded requirement for the Veeam Web Service/API Gateway

. If this port is occupied by another application, the Veeam services will fail to bind, and the application will not start. Veeam Community Resource Hub Common Applications Occupying Port 443 Hyper-V Replication

: If your backup server also acts as a Hyper-V replica server, it often reserves port 443. IIS (Internet Information Services)

: Other web applications or management portals may be bound to the default HTTPS port. Windows Remote Management (WinRM)

: Sometimes conflicts with Veeam's ability to load its console. How to Resolve the Conflict Since port 443 is

and cannot be changed within Veeam v13 itself, you must reconfigure the conflicting application instead. Veeam Community Resource Hub Identify the Occupying Process Open PowerShell as an Administrator. netstat -anob | findstr :443 to find the Process ID (PID) using the port. Match the PID in Task Manager to find the specific software. Reconfigure Hyper-V (If applicable) Hyper-V Settings Replication Configuration Change the specified port from to an alternative (e.g., 444).

Update individual VM replication settings to match the new port. Temporary Workaround for Upgrades

Stop the conflicting service (e.g., IIS or Hyper-V Replication) before starting the Veeam upgrade.

Once the upgrade completes, you may attempt to re-enable the third-party service on a different port. Registry Fix (Veeam Agents only) For standalone Veeam Agents Multiple HTTPS applications : If there are multiple

(not the main VBR server), you can sometimes force a specific port via the registry key mentioned in Veeam KB2332 For further official guidance, refer to the Veeam Help Center used ports

Major Issues After Upgrading to Veeam V13: Port 443 Conflict 11 Dec 2025 —

Step 1: Hyper-V Setting -> Replication Configuration -> Change Specify the Port from 443 to something else. Veeam B&R 13 Change Web Service Port 443 21 Nov 2025 —

When upgrading to Veeam Backup & Replication (VBR) v13 is a strictly required, hardcoded dependency for the new Veeam Web Service/API Gateway

. If this port is occupied by another application, the VBR services will fail to bind, preventing the software from starting or completing an upgrade. Veeam Community Resource Hub Common Conflict Culprits

Port 443 is the standard for HTTPS, making it a high-traffic area. Frequent "squatters" include: Hyper-V Replication: By default, Hyper-V uses 443 for its replication traffic. IIS (Internet Information Services):

Web servers or Microsoft-related services like SQL Reporting Services often bind to this port. Other Web Servers:

Apache, Nginx, or management interfaces for third-party software. How to Identify and Evict the Occupant To reclaim the port for Veeam, follow these steps:

Major Issues After Upgrading to Veeam V13: Port 443 Conflict

Resolving Port 443 Conflicts in Veeam Backup & Replication v13

Veeam Backup & Replication (VBR) v13 introduces a strict requirement for TCP port 443, which is used for the new hardcoded REST API and Web UI services. This shift from previous versions can cause critical installation or upgrade failures if another application—such as IIS, VMware Workstation, or Hyper-V Replication—is already listening on that port. Identifying the Conflicting Application

If you encounter the error "Required port 443... is occupied by another application," you must first identify the process holding the port. Open an elevated Command Prompt or PowerShell. Run the following command:netstat -ano | findstr :443 Locate the PID (Process ID) in the rightmost column.

Find the application name in Task Manager (under the "Details" tab) using that PID. Common Conflicting Services Symptoms of Port 443 Occupation When port 443

Hyper-V Replication: Often uses 443 for HTTPS-based replication.

IIS (Internet Information Services): Default web servers often bind to 443 for HTTPS.

Windows Remote Management (WinRM): Sometimes causes conflicts that prevent the VBR console from loading.

Other Backup Agents: Third-party agents or previous Veeam components might still be holding the port. Solutions and Fixes

In VBR v13, port 443 is hardcoded for the API Gateway and Web service; there is currently no supported way to change this within the Veeam configuration itself. Therefore, you must move the other application to a different port. For Hyper-V Replication Servers: Navigate to Hyper-V Settings > Replication Configuration.

Change the specified port from 443 to a different available port (e.g., 444).

Update the Replica Server Port in the settings for each VM on every host to match the new port. For IIS Sites: Open IIS Manager and expand Sites. Right-click the site using 443 and select Edit Bindings.

Change the HTTPS port to another value or assign the site a specific IP address to free up 443 on "All Unassigned". For WinRM Conflicts:

Reviewers on the Veeam R&D Forums have noted that stopping the Windows Remote Management (WS-Management) service entirely may be necessary if it prevents the console from loading. Next Steps

Before proceeding with your upgrade, verify the full list of required connections in the Veeam Ports List Finder to ensure all other necessary traffic (like ports 2500–3300 for data transfer) is clear. Veeam B&R 13 Change Web Service Port 443

Option C: Stop and Disable the Conflicting Service (Only if not needed)

net stop W3SVC
sc config W3SVC start= disabled

Then restart the Veeam Backup Service:

net stop VeeamBackupSvc
net start VeeamBackupSvc

Step 4: Restart & Retry

After freeing port 443:

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

4. Resolution Steps (Choose One)

Summary

Port 443 (HTTPS) is required by Veeam Backup & Replication for certain components and communication. If another application is already using port 443, replication, console connectivity or web components can fail. This post explains how to identify the conflicting process, safely free or change the port, and validate the fix.

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.

Common Culprits: What is Occupying Port 443?

On a typical Windows Server, the most common offenders are: