This error is a common blocker when upgrading to or installing Veeam Backup & Replication v13 port 443 is now hardcoded and required for the Veeam Web Service and API Gateway

. Unlike previous versions, there is currently no supported way to change this port within the Veeam configuration once the conflict is detected. Veeam Community Resource Hub

To resolve this, you must identify and reconfigure or disable the application currently occupying port 443. 1. Identify the Conflicting Application

Use the command line to find out which Process ID (PID) is using the port: Open Command Prompt as an Administrator. Run the command netstat -ano | findstr :443 Note the PID

: Look for the number in the far-right column for the entry with status Match the PID Task Manager , go to the tab, and find the application matching that PID. Experts Exchange 2. Common Culprits and Fixes

Major Issues After Upgrading to Veeam V13: Port 443 Conflict

This error typically occurs during an upgrade to Veeam Backup & Replication (VBR) v13 or newer, where port 443 is now a hardcoded requirement for the Veeam Web Service and API Gateway. 1. Identify the Conflicting Application

Use the command line to find out exactly what is currently using port 443 on your server.

Step A: Open Command Prompt or PowerShell as an Administrator.

Step B: Run the following command:netstat -ano | findstr :443

Step C: Look for the PID (Process ID) in the right-most column of the result (e.g., 1234).

Step D: Open Task Manager, go to the Details tab, and find the process matching that PID to see what application it belongs to. 2. Common Conflicting Applications The most common culprits occupying port 443 are:

Hyper-V Replication: If your VBR server is also a Hyper-V host with replication enabled, it often claims 443.

IIS (Internet Information Services): Web servers running on the same box.

VMware Workstation: Sometimes uses 443 for its sharing features. 3. Resolution Steps

Because Veeam v13 requires 443 and generally does not support changing this port for its own web services, you must move the conflicting application to a different port.

Major Issues After Upgrading to Veeam V13: Port 443 Conflict

Veeam Backup & Replication relies heavily on specific network ports to facilitate communication between its various components, including the backup server, backup proxies, repositories, and managed servers. One of the most critical ports used by Veeam is Port 443 (HTTPS), which is essential for secure communication, web services, and integration with cloud providers or VMware vSphere environments.

When you attempt to install, upgrade, or start Veeam Backup & Replication services and encounter an error stating that Port 443 is occupied by another application, it can halt your backup operations. This article provides a comprehensive guide to understanding, diagnosing, and resolving this common conflict. 🎯 Direct Answer

To resolve the "Port 443 occupied" error in Veeam Backup & Replication, you must identify the conflicting application using the netstat command or Resource Monitor, and then either stop that application, change its port configuration, or reconfigure Veeam to use an alternative port. 🔍 Understanding the Role of Port 443 in Veeam

Port 443 is the standard port for secure web traffic (HTTPS). In a Veeam environment, it is used for several critical functions:

vSphere Communication: Veeam connects to VMware vCenter Server and ESXi hosts over port 443 to manage snapshots and VM data.

Cloud Connect: Secure connections to Veeam Cloud Connect service providers.

RESTful API: Accessing the Veeam Backup & Replication RESTful API.

Enterprise Manager: Communication between the backup server and Veeam Backup Enterprise Manager.

AWS/Azure Integrations: Secure API calls to public cloud platforms.

If another software package binds to Port 443 on the Veeam server before Veeam can, the Veeam services will fail to start or operate correctly. 🛠️ Step 1: Identify the Conflicting Application

Before you can fix the issue, you need to find out which application has hijacked Port 443. Here are the two most effective methods to do this on a Windows Server. Method A: Using Command Prompt (Netstat)

The fastest way to find the PID (Process Identifier) using port 443 is through the command line. Open Command Prompt as an Administrator. Run the following command:netstat -ano | findstr :443 Look for a line showing LISTENING in the state column. Note the PID listed at the far right of that line.

To find out what that PID is, run:tasklist | findstr [PID_Number] Method B: Using Resource Monitor If you prefer a graphical interface: Press Win + R, type resmon, and hit Enter. Navigate to the Network tab. Expand the Listening Ports section. Click on the Port column to sort numerically.

Locate port 443 and look at the Image column to see the executable name. ⚠️ Common Culprits Occupying Port 443

Several applications frequently conflict with Veeam over Port 443. Common examples include:

Internet Information Services (IIS): Often installed on Windows Servers, hosting default websites on HTTPS.

VMware vCenter/Workstation: If installed on the same machine, VMware services default to port 443.

Skype / Teams: Older desktop versions famously utilized port 443 as a fallback for incoming connections.

Antivirus/Security Software: Local management consoles or update agents.

Web Server Stacks: Apache, Nginx, or XAMPP installed on the backup server. 🚀 Step 2: Resolving the Conflict

Once you have identified the application holding the port, choose one of the following remediation paths. Option 1: Stop or Uninstall the Conflicting Application

If the application occupying the port is not needed on your Veeam Backup server, the cleanest solution is to remove it.

Open services.msc and stop the offending service (e.g., World Wide Web Publishing Service for IIS).

Set the service startup type to Disabled to prevent it from grabbing the port after a reboot. Option 2: Change the Port of the Conflicting Application

If you must run both applications on the same server, change the port used by the non-Veeam application.

For IIS: Open IIS Manager, select the site, click Bindings in the right pane, edit the HTTPS binding, and change port 443 to an unused port (e.g., 8443).

For Apache: Edit the httpd.conf or ssl.conf file and change Listen 443 to another port. Option 3: Change the Port in Veeam

If you cannot change the port of the other application, you can reconfigure Veeam to use a different port for its web UI or API components during installation or via the registry/configuration files.

Note: Changing default ports in Veeam should be done with caution and documented, as you will need to specify the custom port when connecting external components or accessing web consoles. 💡 Best Practices for Veeam Port Management

To avoid running into these issues in the future, follow these industry best practices:

Dedicated Backup Server: Never install Veeam Backup & Replication on a machine running IIS, Active Directory, or vCenter. Keep the backup server dedicated.

Pre-Install Port Audits: Run netstat before installing Veeam to ensure ports 443, 6160, 9392, and 11560 are completely free.

Firewall Segmentation: Ensure internal Windows firewalls are configured to allow Veeam traffic explicitly rather than opening ports globally.

This error commonly occurs during upgrades to Veeam Backup & Replication (VBR) v13, which now requires port 443 for its REST API and Web UI services. In newer versions, this port is often hardcoded and mandatory, meaning the installer will block the upgrade if it is already in use by another application. Phase 1: Identify the Conflicting Application

Before you can resolve the conflict, you must find which process is currently listening on port 443. Run Command Prompt as Administrator. Execute the netstat command:netstat -ano | findstr :443

Identify the PID: Look at the rightmost column for the Process Identifier (PID) (e.g., 1234). Find the application name: Open Task Manager (Ctrl+Shift+Esc).

Go to the Details tab and sort by the PID column to find the matching application.

Common culprits include Hyper-V Replication, IIS (Internet Information Services), Windows Remote Management (WinRM), or third-party monitoring tools. Phase 2: Resolve the Conflict

Since port 443 is often required and hardcoded for the Veeam Web service/API Gateway in v13, you generally have two options: reconfigure the other application or temporarily stop it during the upgrade. Option A: Reconfigure the Conflicting Application

Hyper-V Replication: If the Veeam server also acts as a Hyper-V Replica server, change the Hyper-V replication port from 443 to something else (e.g., 444) in Hyper-V Settings > Replication Configuration.

IIS Web Sites: If another site is using 443, change its binding in the IIS Manager to a different port or a specific IP address.

Windows Remote Management (WinRM): In some cases, the WinRM service or WS-Management must be stopped to allow the Veeam console to load correctly. Option B: Temporary Stop for Upgrade Veeam B&R 13 Change Web Service Port 443

Method B: Using PowerShell (More Detail)

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

Common Symptoms of the Error

Before diving into fixes, recognize how this error manifests:

  1. During fresh installation: The pre-installation scan fails with a red "Failed" status next to port 443.
  2. During upgrade: The upgrade wizard rolls back or pauses, citing port conflict.
  3. After installation: The Veeam Backup Service remains in "Starting" state and eventually stops.
  4. In event logs: System log entries show HTTP Error 0x800700b7 or Failed to register URL prefix https://+:443/.
  5. Console access: The Veeam Backup & Replication console fails to connect to the local backup server.

Summary

While it is possible to force Veeam to use alternate ports, the industry-standard approach is to dedicate the backup server to Veeam workloads. Resolving the port conflict by moving or removing the conflicting application (usually IIS) ensures that Veeam operates within its default architectural design, minimizing connectivity issues with remote repositories and guest proxies in the future.

In Veeam Backup & Replication (VBR) v13, port 443 is a hardcoded requirement for the REST API/Web UI service and cannot be changed through any supported method. If this port is occupied, the VBR services will fail to bind, and your installation or upgrade will be blocked.

To resolve this conflict, you must identify and reconfigure the competing application. 1. Identify the Occupying Application

Use the command line to find which process is currently using port 443. Run CMD as Administrator: Type netstat -aon | findstr :443.

Locate the PID: The number at the far right of the output is the Process ID (PID).

Check Task Manager: Open Task Manager, go to the Details tab, and find the application matching that PID. 2. Common Conflicts and Solutions

The most frequent culprits on Windows Servers are often built-in Microsoft services:

Major Issues After Upgrading to Veeam V13: Port 443 Conflict

Veeam Backup & Replication (VBR) v13 is now a mandatory, hardcoded requirement for the Veeam Web Service and API Gateway. If this port is occupied by another application, the VeeamBackupRESTSvc

will fail to start, potentially blocking your upgrade or regular operations. 1. Identify the Conflicting Application

Before you can resolve the conflict, you must find which service is currently using port 443. Command Line : Open Command Prompt as Administrator and run: netstat -ano | findstr :443 Identify the Process : Note the (Process ID) in the far-right column. Cross-Reference in Task Manager Task Manager (Ctrl+Shift+Esc). Find the application matching your PID. PowerShell Alternative Get-NetTCPConnection

Get-NetTCPConnection -LocalPort 443 | Select-Object LocalPort, OwningProcess, State 2. Resolve Common Conflicts There is currently no supported method

to change the port 443 requirement within Veeam v13. Instead, you must reconfigure or move the conflicting application. Hyper-V Replication

: If the VBR server is also a Hyper-V Replica server, Hyper-V likely owns port 443. : Change the Hyper-V Replication port (e.g., to 444) in Hyper-V Settings Replication Configuration . You must also update this on each replica VM. IIS / Web Servers

: If Internet Information Services (IIS) is installed, it often claims 443 for the "Default Web Site." : Change the site bindings in IIS Manager or stop the service if it is not required. Antivirus/Security Agents

: Some security software uses 443 for local management consoles.

: Check if the management port can be reconfigured in the vendor's settings. Veeam B&R 13 Change Web Service Port 443

In Veeam Backup & Replication (VBR) v13, port 443 is a critical requirement for the new Veeam Web UI and REST API gateway. If this port is occupied by another application, the VBR installation or upgrade will fail, or services will not start correctly because the binding is "hardcoded" for these components. Identifying the Conflicting Application

To find out what is currently using port 443 on your Windows server: Open Command Prompt as an Administrator.

Run the following command to find the Process ID (PID) using the port:netstat -aon | findstr :443 Note the PID (the number in the far-right column).

Identify the process name by opening Task Manager, going to the Details tab, and sorting by the PID column. Common Conflicting Applications

IIS (Internet Information Services): Often bound to port 443 for web hosting.

Hyper-V Replication: If the server is configured as a Hyper-V Replica server, it may use 443 by default.

Other Backup Software or Monitoring Tools: Applications with their own web-based management consoles frequently occupy this port. Resolution Strategies Veeam B&R 13 Change Web Service Port 443

9. Node.js, Nginx, or Apache running as a service

Developer tools or web servers left running from previous projects.

Target audience

System administrators and backup engineers with intermediate knowledge of Windows Server, networking, and Veeam.

Introduction

Veeam Backup & Replication is widely regarded as the gold standard for data protection in virtual, physical, and cloud environments. However, even the most robust platforms can encounter installation or upgrade issues. One of the most frustrating and frequently reported errors during Veeam deployment or service restart is:

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

This message halts installations, prevents service startups, and leaves administrators scrambling to identify the unknown "application" blocking the port. Given that port 443 is the default HTTPS port used globally for secure web traffic, conflicts are not only common but can be tricky to resolve without collateral damage to other services.

In this deep-dive article, we will explore:
A woman hugs her daughter

KEEP UP WITH THE ACTION

Join our community of supporters passionate about ending world hunger.

This field is for validation purposes and should be left unchanged.