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

The blinking cursor on the dashboard monitor felt like a heartbeat, and not a calm one. It was 2:00 AM on a Sunday, the window for the off-site backup chain to close in exactly fifty-five minutes.

Elias, the senior systems engineer, gripped his coffee mug like a lifeline. The Veeam Backup & Replication console was displaying a sea of red. The job—dubbed "Critical-VMs-Offsite"—had failed. Again.

He clicked the "Details" link, his eyes scanning the error log until they locked onto the fatal sentence:

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

Elias sighed, the sound heavy in the empty server room. Port 443. The golden gate of network traffic. The standard port for HTTPS, essential for the Veeam Backup Catalog to communicate with the repository server over WAN accelerators. Without it, the backup chain was dead in the water.

"Who stole the port?" he whispered to the hum of the cooling fans.

He opened a PowerShell terminal with administrator privileges. His fingers flew across the keyboard, invoking the network investigation.

netstat -ano | findstr :443

The screen flickered and returned a list. He ignored the established connections from the web servers; he was looking for the state LISTENING. There it was.

TCP 0.0.0.0:443:0 LISTENING 4988

Process ID 4988. The culprit.

Elias frowned. On the repository server (Repo-01), the only things running should have been the Veeam Data Mover service and basic OS functions. He ran the tasklist command to identify the owner of PID 4988.

tasklist /svc /fi "PID eq 4988"

The result made his blood run cold: vmware-hostd.exe.

"VMware?" Elias muttered, pushing back from his desk. "That doesn't make sense. This is a bare-metal repository, not an ESXi host."

He stood up and walked down the cold aisle of the data center, the blue lights of the server racks casting long shadows. He stopped in front of the rack containing Repo-01. It was a sturdy Dell PowerEdge, purchased specifically for heavy storage throughput.

He connected a crash cart—a keyboard and monitor directly into the server.

"Okay," Elias said, logging in. "What are you hiding?"

He opened the services.msc snap-in. Sure enough, the VMware Workstation Server service was running. But who installed VMware Workstation on a production backup repository?

Then, a memory flashed in his mind. Two days ago. The Junior Admin, Kevin. The blinking cursor on the dashboard monitor felt

"Hey Elias," Kevin had said, looking slightly nervous. "I needed to spin up a quick test lab to simulate that patch for the accounting software. I didn't want to bother the production cluster, so I just threw it on the repo server since it has all that RAM. Is that cool?"

Elias had dismissed him with a wave. "Just make sure it doesn't impact IOPS."

Elias rubbed his temples. Kevin had installed the management interface of VMware Workstation. By default, that interface grabs Port 443 to serve its web console. It was a silent conflict. Veeam had been working fine until the service restarted tonight, tried to bind to 443, and found the door already locked by VMware.

Time was ticking. 2:15 AM.

He had two choices.

Uninstall VMware Workstation. (Too slow, required a reboot).
Reconfigure the VMware service to use a different port.

He checked the Veeam logs again. The backup job was retrying in ten minutes. He needed a surgical fix.

He navigated to the VMware Workstation installation directory. He needed to edit the config.ini file located in the application data folder, or better yet, change the service configuration via the GUI if he could load it. He tried to open the VMware console, but it was sluggish.

"Come on," he hissed.

He decided to force the issue via the Registry Editor. It was the nuclear option, but precise.

He navigated to HKLM\SOFTWARE\WOW6432Node\VMware, Inc.\VMware Workstation.

He looked for the httpPort key. There it was, staring back at him: 443.

He changed the value to 8443. Then, he opened the Services console, located the VMware Workstation Server service, and hit Restart.

The status bar moved agonizingly slow. Starting... Starting...

Elias glanced at his watch. 2:22 AM.

Started.

Now for the moment of truth. He needed to stop the Veeam Data Mover service and restart it so it could re-bind to the now-available port.

net stop "VeeamBackupSvc" net start "VeeamBackupSvc"

The service started cleanly. No errors. No conflicts.

He rushed back to his desk in the other room, the wheels of his chair squeaking loudly. He pulled up the Veeam console. The job was set to "Idle". He right-clicked the failed job. Uninstall VMware Workstation

"Retry".

The window popped up. Initializing... Connecting to host... Preparing metadata...

He held his breath. If the port was still blocked, it would fail instantly. Processing VM "SQL-01"...

The progress bar hit 1%. Then 2%.

Elias exhaled, a long, shaky breath. The port was free. The backup was running.

He made a mental note to have a very serious conversation with Kevin about lab hygiene on Monday morning. But for now, he watched the green progress bar crawl across the screen, the data flowing safely through the reclaimed Port 443, securing the company's future one megabyte at a time.

Let's dive deep into the issue of port 443 being occupied by another application when trying to use it for Veeam Backup replication.

Understanding the Issue

Veeam Backup & Replication uses various ports for communication between components, including the Veeam Backup Server, Proxy Servers, and Repository Servers. One of these ports is TCP 443, which is typically used for HTTPS traffic.

When you try to configure Veeam Backup replication, you may encounter an error message indicating that port 443 is already in use by another application. This can be frustrating, especially if you're not aware of what application is using the port.

Common Causes of Port 443 Occupation

Here are some common causes of port 443 being occupied:

Other backup or replication software: Another backup or replication software might be using port 443 for its own communication. Examples include other backup solutions like Commvault, NetBackup, or Data Protection Manager.
Web servers or IIS: If you have a web server or IIS (Internet Information Services) installed on the same machine as your Veeam Backup Server, it may be using port 443 for HTTPS traffic.
SSL/TLS certificates or services: Services like Certificate Authority (CA) servers or SSL/TLS certificate management tools might use port 443 for certificate-related communication.
Other applications or services: Any other application or service that uses HTTPS or SSL/TLS might be occupying port 443.

How to Identify the Occupying Application

To identify which application is using port 443, follow these steps:

On Windows:

Open a Command Prompt as an administrator.
Run the command: netstat -anop | findstr 443
This will list all processes using port 443. Look for the PID (Process ID) of the process using the port.

On Linux:

Open a Terminal.
Run the command: netstat -tlnp | grep 443
This will list all processes using port 443. Look for the PID (Process ID) of the process using the port.

Once you've identified the occupying application, you can:

Stop the occupying application: If possible, stop the application or service using port 443.
Change the occupying application's port: If possible, change the port used by the occupying application to a different port.
Configure Veeam Backup to use a different port: You can configure Veeam Backup to use a different port for replication. To do this, go to Veeam Backup & Replication > Settings > Network > Ports, and change the Port value for Replication to a different port (e.g., 4433).

Additional Considerations

When changing ports, consider the following: He checked the Veeam logs again

Ensure that any firewalls or network access control lists (ACLs) are updated to allow traffic on the new port.
Verify that all Veeam Backup components (e.g., Backup Server, Proxy Servers, Repository Servers) are configured to use the new port.
If you're using a load balancer or reverse proxy, you may need to update its configuration to route traffic to the new port.

By following these steps and considerations, you should be able to resolve the issue of port 443 being occupied by another application when trying to use it for Veeam Backup replication.

Changing Veeam’s Port 443 During Installation

Start the Veeam setup wizard.
On the Service Account Configuration or Ports Configuration screen (varies by version), locate the field for Veeam Backup Service port (HTTPS).
Change 443 to an alternative like 8443 or 9443.
Complete the installation.

Important: Changing Veeam’s port impacts:

REST API calls (must now use https://<server>:8443).
Enterprise Manager integration (must be reconfigured).
Guest interaction proxies (update firewall rules).

References / Further reading

Veeam KB articles and official port requirements (search Veeam help for "ports used by Veeam Backup & Replication").
Microsoft docs for HTTP.sys, netsh, and IIS bindings.
Docker and reverse-proxy documentation for port mapping and host networking.

This error typically occurs during the installation or upgrade to Veeam Backup & Replication v13 (or newer), as port 443 is now hardcoded and required for the Veeam Web Service/API Gateway

. Because this port is fixed, the Veeam services will fail to bind and start if another application is already using it Quick Fixes for Common Conflicts

If you encounter this conflict, identify the application using port 443 and apply the relevant solution: Hyper-V Replication Conflict

: This is a common issue if the VBR server is also a Hyper-V Replica server Hyper-V Settings Replication Configuration Change the port from to something else (e.g., 444)

Update the replica settings for each VM to match this new port Windows Remote Management (WinRM)

: In some environments, WinRM or WS-Management may occupy this port Temporarily stop the Windows Remote Management

service to allow the Veeam console to load or complete its upgrade General Web Services

: Other web servers (like IIS or Apache) or third-party monitoring tools may be using port 443. Identify the process : Open a command prompt as an administrator and run netstat -anob | findstr :443

. This will tell you the PID (Process ID) of the application occupying the port Workaround

: Stop the conflicting service during the Veeam upgrade. While Veeam Support

may suggest stopping it just for the installation, the VBR console may still fail to work later if the conflict returns Important Compatibility Notes Port is Hardcoded : In version 13.0.1.180 and newer, there is no supported method to change this port for the internal Veeam Web service Database Compatibility : Ensure your SQL database is at least SQL Server 2016

or newer, as v13 requires this compatibility level to function Firewall Rules

: Veeam usually creates its own firewall rules, but you must ensure no external network firewalls are blocking 443 communication between the backup server and its components PowerShell commands to identify exactly which process is holding that port?

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

Step 3: The "Hidden" Conflict (WinRM)

Sometimes, netstat shows that the "System" process is listening on 443, but IIS is not installed. This is often caused by Windows Remote Management (WinRM) listening on port 443 for HTTPS listeners.

To check and remove this listener:

Open PowerShell as Administrator.
Check current listeners:
```
winrm enumerate winrm/config/listener
```
If you see a listener on Port 443, you can delete it:
```
winrm delete winrm/config/listener?Address=*+Transport=HTTPS
```
(Note: Be careful with this command if this server relies on WinRM for remote management via PowerShell.)

1. Executive Summary

Veeam Backup & Replication (VBR) requires TCP port 443 for core functionalities, including:

Veeam Backup Service communication.
RESTful API services (Veeam Backup Enterprise Manager).
Cloud Connect and vCloud Director integrations.
Mount Server operations.

When another process binds to port 443 before Veeam starts, the Veeam Backup Service fails to initialize. This report outlines the causes, detection methods, and step-by-step resolution procedures.

Step 2: Resolution Strategies

There are two main ways to resolve this: change the port for the conflicting application (Recommended) or configure Veeam to use a different port.