Required Port 443 For Veeam Backup Replication Is Occupied By Another Application Link
In the complex ecosystem of data center management, Veeam Backup & Replication has established itself as a gold standard for virtualization and cloud data protection. However, even the most robust platforms can encounter frustrating roadblocks. One of the most common and cryptic errors that administrators face during installation or upgrade occurs when Veeam attempts to bind to Port 443.
The full error typically reads:
"Required port 443 for Veeam Backup & Replication is occupied by another application. Please specify another port or stop the application that uses this port and try again."
While the error message seems straightforward—"another app is using the port"—the resolution is rarely a simple matter of killing a process. Port 443 is the default port for HTTPS (HTTP Secure) traffic, and in a Windows Server environment, multiple roles, services, and third-party applications compete for it.
This article provides a definitive, step-by-step guide to diagnosing why Port 443 is occupied on your Veeam server and how to safely resolve the conflict without breaking existing services.
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.
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.
"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.
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. In the complex ecosystem of data center management,
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.
"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.
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
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
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. "Required port 443 for Veeam Backup & Replication
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
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
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
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
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:
"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."
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) Depending on what you find
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 —
When upgrading to or installing Veeam Backup & Replication (VBR) v13, many administrators encounter the error: "Required port 443 for Veeam Backup & Replication is occupied by another application". This occurs because port 443 is now hardcoded for the mandatory Veeam REST API Service and Web UI in version 13. Why Port 443 is Required
In Veeam v13, port 443 is used for the Identity Service and REST API Gateway. If another service is already listening on this port, the Veeam services will fail to bind, preventing the VBR console from starting or the upgrade from completing. How to Identify the Conflicting Application
To resolve the conflict, you must first identify which process is currently using port 443.
Command Line: Open a command prompt as administrator and run netstat -anob | findstr :443. This will display the Process ID (PID) and the name of the executable using the port.
PowerShell: Use the command Get-NetTCPConnection -LocalPort 443 to find the associated PID.
Common Culprits: Frequently conflicting services include IIS (Internet Information Services), Hyper-V Replication, Remote Desktop Web Access, or third-party security agents like Qualys. Solutions and Workarounds
Currently, there is no supported method within the Veeam installer to change the port for the REST API Gateway. You must free up the port on the host server: Stop or Reconfigure the Conflicting Service:
If IIS is using the port, you can change its binding via the IIS Manager (InetMgr.exe) by selecting "Edit Bindings" for the website and changing 443 to a different port.
If Hyper-V Replication is the cause, go to Hyper-V Settings > Replication Configuration and change the port from 443 to another value (e.g., 444).
Temporary Stop for Upgrade: If the conflicting application is only needed occasionally, stop the service, complete the Veeam v13 upgrade, and then attempt to restart the other service. Note that Veeam v13 services will still fail to start if the port is occupied later.
Use a Dedicated Server: Veeam recommends installing VBR on a dedicated server to avoid port conflicts with other web-facing applications. Troubleshooting Connectivity
Major Issues After Upgrading to Veeam V13: Port 443 Conflict
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.
Port 443 is the standard HTTPS port. Common applications that conflict with Veeam include:
| Application / Service | Typical Context | |----------------------|------------------| | IIS (Internet Information Services) | Default web server on Windows; may host other websites or management consoles. | | Microsoft Exchange Server | Uses port 443 for Outlook Web Access (OWA) and Exchange Admin Center. | | Skype for Business / Teams (on-prem components) | Uses port 443 for web conferencing and mobility services. | | Apache / Nginx | Third-party web servers running on same Windows VBR server. | | VMware vCenter Server (embedded) | If Veeam is installed on a vCenter Server (not recommended). | | SQL Server Reporting Services (SSRS) | Uses port 443 for report manager. | | Third-party antivirus / proxy services | Some inject a local HTTPS inspection proxy. |
netstat -ano | findstr :443
net stop W3SVC
sc config W3SVC start= disabled
Then restart the Veeam Backup Service:
net stop VeeamBackupSvc
net start VeeamBackupSvc
Depending on what you find, take the appropriate action:
If you can’t stop the other application (e.g., it’s another critical backup tool), you have two options: