Required Port 443 For Veeam Backup & Replication Is Occupied By Another Application _verified_

Here’s a detailed, practical blog-style post you can use directly or adapt for your audience.

Title: Troubleshooting "Port 443 Required for Veeam Backup & Replication is Occupied by Another Application"

Introduction

You’re installing or upgrading Veeam Backup & Replication, and suddenly you hit a roadblock:

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

Port 443 is critical—it’s used by Veeam Backup Service for secure HTTPS communication between Veeam components (e.g., backup server, consoles, and guest interaction proxies). When another process claims it, the installation won’t proceed. Here’s how to identify and resolve the conflict quickly.

Step 1: Identify the Occupying Application

Open an elevated Command Prompt or PowerShell and run:

netstat -aon | findstr :443

Look for the listening process (state LISTENING). Note the PID (Process ID) in the last column.

Then, find the process name:

tasklist | findstr <PID>

Or in PowerShell:

Get-Process -Id (Get-NetTCPConnection -LocalPort 443).OwningProcess

Common culprits:

  • IIS / IIS Express – Default HTTPS binding
  • Skype, Teams, or Discord – They sometimes reserve ports
  • Another Veeam installation (e.g., a second instance)
  • Nginx, Apache, or third-party web servers
  • SQL Server Reporting Services (SSRS)
  • VMware vSphere Client (on same machine – not typical but possible)

Step 2: Stop the Conflicting Service

Once you know the process, decide whether to stop it or reconfigure it.

Case A – Unnecessary application (e.g., Skype, Teams):

  • Close the app, or go into its advanced settings to disable port 443 usage.
  • Stop the service permanently: services.msc → locate service → Stop & set Startup type to Disabled.

Case B – IIS with its default site:

  • Open IIS Manager → Select the site binding on port 443 → Remove or change to another port (e.g., 8443).
  • Or stop the IIS service: iisreset /stop or disable the World Wide Web Publishing Service.

Case C – Another legitimate service you need (e.g., SSRS):

  • Reconfigure that service to use a different port (e.g., 4443). Check its configuration files or management console.

Step 3: Verify the Port is Free

After stopping/removing the conflict, run:

netstat -aon | findstr :443

Ensure no process is listening on 0.0.0.0:443 or [::]:443.

Step 4: Retry Veeam Installation

Resume the Veeam Backup & Replication setup. The port check should now pass. If you still see the error, reboot the server and check again—some processes release ports only after a full restart.

What if the conflicting process is Veeam itself?

If netstat shows the Veeam Backup Service (e.g., Veeam.Backup.Service.exe) on port 443 but the installer still complains, you may have a stale installation. In that case:

  1. Stop all Veeam services.
  2. Run the Veeam installer in Remove mode.
  3. Reboot and install fresh.

Prevention Tips for Future Deployments

  • Dedicated Veeam server – Avoid installing other web services on the same machine.
  • Change Veeam’s port if necessary – During advanced installation, you can specify a different port (not recommended for production unless you have a conflict you can’t resolve).
  • Pre-flight checklist – Before installing Veeam, run a port scan on the target server.

Final Thoughts

Port 443 conflicts are common but easy to fix once you know what’s listening. In most cases, it’s a harmless local service like IIS or a chat app. By identifying the PID and stopping or reconfiguring the offender, you’ll get Veeam Backup & Replication installed without a hitch.

Have you encountered other unexpected services blocking Veeam ports? Let me know in the comments.

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. Here’s a detailed, practical blog-style post you can

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

This is a common and critical issue when deploying Veeam Backup & Replication (VBR). The error indicates a port conflict on TCP port 443.

Veeam Backup & Replication requires TCP Port 443 specifically for its Veeam Backup Service. This service acts as the secure communication channel (using HTTPS) between the Veeam Backup Server, Backup Proxies, Backup Repositories, and Managed Servers (vCenter/ESXi/Hyper-V).

Because Port 443 is the standard port for HTTPS traffic, it is frequently claimed by other services (most notably IIS, WSUS, or other web applications) running on the same Windows Server.

Here is a detailed breakdown of the feature, the conflict, and the resolution.

Troubleshooting: Port 443 Conflict with Veeam Backup & Replication

Phase 3: Resolve the Conflict

Based on the identified process:

Descriptive examination: "Required port 443 for Veeam Backup & Replication is occupied by another application"

D. Use port exclusion (HTTP.sys)

If the conflict is with another HTTP.sys reservation, remove the other reservation: Title: Troubleshooting "Port 443 Required for Veeam Backup

netsh http delete urlacl url=https://+:443/

(Be careful – this removes all HTTPS:443 reservations for non-admins.)

8. When to Contact Veeam Support

  • If no other application appears to be using 443, but Veeam still claims it is occupied (possible Windows HTTP.sys corruption).
  • After removing the conflicting app, port 443 remains locked (requires reboot or net stop http /y).
  • Veeam services fail even after freeing port 443 (check other Veeam-specific ports: 9392, 9393, 6160, etc.).