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

Before you can fix the issue, you must determine which application is currently listening on port 443. You can do this via the Command Line or PowerShell.

The error "Required port 443 for Veeam Backup & Replication is occupied by another application" is rarely a sign of Veeam being broken; rather, it highlights a classic Windows port contention issue. By methodically identifying the process using netstat, removing HTTP.SYS reservations, reconfiguring IIS or SSRS, or changing Veeam’s own port, you can resolve the conflict in under 15 minutes.

Remember, port 443 is prime real estate. Decide which application—Veeam or the existing service—is more critical for your environment, then adjust accordingly. With the steps above, you’ll have Veeam Backup & Replication listening securely and ready to protect your data.

Need further assistance? Visit the official Veeam R&D Forums or open a support case with Veeam Customer Support. Include the output of veeamportssniffer.exe (available in the Veeam ISO tools folder) for rapid troubleshooting.

The error "Required port 443 for Veeam Backup & Replication is occupied by another application" typically occurs during an upgrade to Veeam Backup & Replication (VBR) v13, as this version introduces a hardcoded requirement for port 443 for its REST API and Web UI. Review of Issue & Solutions

Industry feedback indicates this is a significant hurdle for environments where port 443 is already used by other critical services like Hyper-V Replication or third-party web applications.

Upgrade Blockage: The VBR v13 installer strictly blocks upgrades if port 443 is in use. There is currently no supported way to change this port within Veeam or bypass the check.

Common Culprit - Hyper-V: A frequent cause is the Hyper-V Replica service on the same server. An "easy fix" reported in Veeam R&D Forums involves changing the Hyper-V replication port from 443 to another value (e.g., 444) before proceeding with the Veeam upgrade.

Troubleshooting Tool: Users on Reddit recommend running netstat -anob in an elevated command prompt to identify the specific process ID (PID) currently bound to port 443.

Official Guidance: Veeam KB4557 advises that if third-party software is using the port, it is generally better to reconfigure that software rather than trying to modify Veeam's expected configuration. Summary of Resolution Steps

Identify the Conflict: Use netstat -anob to find what service is using 443.

Temporary Workaround: Stop the conflicting service long enough to complete the Veeam upgrade. Permanent Fix:

If it is Hyper-V Replication, change the port in Hyper-V Settings > Replication Configuration.

If it is a web service (like IIS or Apache), move that service's SSL binding to a different port.

Consult the Veeam Ports Guide to ensure no other required ports are blocked.

Major Issues After Upgrading to Veeam V13: Port 443 Conflict

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

(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 — Before you can fix the issue, you must

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 —

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

Resolving Port 443 Conflicts in Veeam Backup & Replication Veeam Backup & Replication is the backbone of many disaster recovery strategies, but its installation or operation can come to a screeching halt when a "Port 443 occupied" error appears. Because Port 443 is the industry standard for HTTPS traffic, it is highly contested by web servers, monitoring tools, and communication platforms.

If you are seeing errors indicating that required port 443 for Veeam Backup & Replication is occupied by another application, this guide will help you identify the culprit and clear the path for your backups. Why Veeam Needs Port 443 Veeam uses Port 443 for several critical functions:

RESTful API Service: Modern Veeam components communicate via HTTPS.

Cloud Connect: Securely transmitting data to service providers.

vSphere Integration: Communicating with VMware vCenter or ESXi hosts.

Veeam Backup Enterprise Manager: Providing the web-based management interface.

When another service grabs this port first, Veeam cannot bind its services, leading to failed installations or "Service Unreachable" errors. Step 1: Identify the "Occupying" Application

Before you can fix the conflict, you need to know what is sitting on the port. Open PowerShell or Command Prompt as an Administrator.

Run the following command to find the Process ID (PID) using Port 443: powershell netstat -ano | findstr :443 Use code with caution.

Look for the line that says LISTENING. The number at the far right is the PID. To see which application owns that PID, run: powershell tasklist /fi "pid eq [YOUR_PID_HERE]" Use code with caution. Common Culprits

IIS (Internet Information Services): Often used for other web applications on the same server.

VMware Workstation/Player: The "VMware Host Agent" often claims 443.

Skype/Teams: Older versions of communication tools sometimes default to 443.

Antivirus/EDR Agents: Some security consoles use 443 for local communication. Step 2: Resolve the Conflict

You have three primary ways to fix this, depending on your environment. Option A: Disable or Move the Conflicting Service

If the application occupying the port isn't vital to that specific server, the easiest fix is to stop it.

For IIS: Change the "Default Web Site" binding from 443 to another port (like 4443) via the IIS Manager.

For VMware Workstation: Go to Edit > Preferences > Shared VMs and change the port or disable sharing. Option B: Change Veeam’s Default Port Need further assistance

If you are performing a fresh installation, Veeam allows you to specify the ports. If the system is already installed, changing the port is more complex and involves the registry or the Veeam Configuration backend.

Warning: Changing Veeam's default ports may require you to update firewall rules and re-authenticate connected components. Option C: Use a Dedicated Backup Server

Best practice dictates that a Veeam Backup Management Server should ideally be a dedicated role. If your server is acting as a Web Server (IIS), a Print Server, and a Backup Server, port conflicts are inevitable. Moving Veeam to its own VM or a dedicated physical box eliminates this issue entirely. Step 3: Verify the Fix

Once you have stopped the conflicting application or reassigned the port, restart the Veeam services: Open services.msc. Locate Veeam Backup Service. Right-click and select Restart.

Check the netstat -ano | findstr :443 command again to ensure the Veeam PID is now the one listening.

The "Port 443 occupied" error is a common networking hurdle, not a flaw in the Veeam software. By identifying the PID using netstat and either relocating that application or dedicating the server to Veeam, you can ensure your data protection environment remains stable and secure.

The "Required port 443 for Veeam Backup & Replication is occupied by another application" error typically occurs when upgrading to Veeam Backup & Replication (VBR) v13. In this version, port 443 is hardcoded for the new Veeam Web Service/API Gateway and cannot be changed through standard supported methods. Identifying the Conflicting Application

To resolve the conflict, you must first identify which application is currently using port 443:

Command Line: Run netstat -aon | findstr :443 in an elevated Command Prompt. The last column displays the Process ID (PID) using the port.

PowerShell: Use Get-NetTCPConnection -LocalPort 443 | Select-Object OwningProcess to find the PID, then use Get-Process -Id to identify the specific application name.

Task Manager: Match the PID found in the steps above to the list under the Details tab to see the application's name and location. Common Conflicts and Fixes The most frequent culprits for this conflict include: Veeam B&R 13 Change Web Service Port 443

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

. If this port is occupied by another application, the VBR v13 installer will block the upgrade or installation until the conflict is resolved Why Port 443 is Required Veeam Web Service

: VBR v13 introduces a mandatory web interface and API gateway that listens specifically on port 443 Licensing & Updates

: It is used to validate user activities, update licenses, and communicate with the Veeam License Update Server Compatibility Checks

: The installer performs a pre-install check; if 443 is in use, the "Required port 443 is occupied by another application" error triggers Common Conflicting Applications Hyper-V Replication : Often uses 443 for HTTPS replication traffic IIS (Internet Information Services)

: Standard web servers or other management consoles frequently bind to this port SQL Server Reporting Services : May be configured to use 443 for web access. Other Monitoring Tools

: Third-party agents (e.g., Datadog) sometimes occupy management ports Recommended Solutions Currently, there is no supported method to change the port for the Veeam Web Service in VBR v13, as it is hardcoded . To proceed, you must move the application to a different port:

Major Issues After Upgrading to Veeam V13: Port 443 Conflict

Step 1: Hyper-V Setting -> Replication Configuration -> Change Specify the Port from 443 to something else. re-replicate the VM. R&D Forums Veeam B&R 13 Change Web Service Port 443

Topic: Port 443 Conflict Preventing Veeam Backup & Replication Service Initialization Severity: High (Service Disruption) Common Error Message: Unable to start Veeam Backup Service. The required port 443 is already occupied by another application.

By identifying the process holding the port and deciding whether to move the intruder or move Veeam, you can resolve the installation error and get your backup infrastructure up and running.

Here’s a properly worded version of your message:

"Port 443, required for Veeam Backup & Replication, is occupied by another application."

If you want to keep it closer to your original structure: This error occurs when another service is using

"Port 443, which is required for Veeam Backup & Replication, is currently occupied by another application."

Or more concisely (e.g., for an alert or log message):

"Required port 443 for Veeam Backup & Replication is in use by another application."

In 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 during installation or upgrade, the Veeam services will fail to bind and start. Identifying the Conflicting Application

Before resolving the conflict, identify which process is currently using port 443.

Command Prompt: Open CMD as Administrator and run:netstat -anob | findstr :443

PowerShell: Use this command to find the specific process name:Get-Process -Id (Get-NetTCPConnection -LocalPort 443).OwningProcess Common Applications Causing Conflicts

Hyper-V Replication: If the VBR server also acts as a Hyper-V Replica server, it may already be using 443 for HTTPS replication.

IIS (Internet Information Services): Web servers hosted on the same machine often default to 443 for HTTPS.

VMware vCenter/ESXi: If VBR is installed on a machine with other management tools, they may occupy the port. Resolution Steps

Because port 443 is currently hardcoded and cannot be changed within Veeam v13 settings, you must reconfigure the conflicting application. Option 1: Reconfigure Hyper-V Replication (If Applicable) If Hyper-V is the culprit, change its replication port: Go to Hyper-V Settings > Replication Configuration.

Change the Specify the Port value from 443 to a different port (e.g., 444).

Update the replication settings for each individual VM on the host to match the new port. Option 2: Temporary Service Suspension If the conflicting application is only needed occasionally:

Stop the conflicting service (e.g., IIS or a custom web app). Complete the Veeam VBR v13 upgrade or installation.

Attempt to restart the original service on a different port if possible. Option 3: Use a Dedicated Backup Server

Veeam best practices recommend installing VBR on a dedicated server to avoid resource and port conflicts. If port 443 is essential for a primary line-of-business application on that server, migrating Veeam to a separate VM or physical host is the most stable long-term solution.

For deeper connectivity troubleshooting, you can refer to the Veeam Ports Finder Tool to map out all required communications.

Blog Title: Troubleshooting Veeam: "Port 443 is Required but Occupied by Another Application"

Meta Description: Struggling with Veeam Backup & Replication installation? Learn how to identify the process hogging port 443 and resolve the conflict quickly.

We’ve all been there. You’re in the middle of deploying or updating Veeam Backup & Replication, feeling confident, when suddenly the wizard stops you dead in your tracks with the dreaded error:

"Port 443 is required for Veeam Backup & Replication but is currently occupied by another application."

Port 443 is the default for HTTPS—Veeam needs it for communication between the backup server, proxies, repositories, and the WAN accelerator (especially for Cloud Connect or guest interaction proxies). If something else has claimed that port, your installation won’t proceed.

Let’s break down how to identify the culprit, fix the conflict, and get your Veeam deployment back on track.

Windows:

Find the process name from the PID:

tasklist /fi "PID eq <PID>"

Or in PowerShell:

Get-Process -Id <PID>

Linux (if applicable):

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