Fix: Veeam Port 443 Occupied by Another Application When upgrading to Veeam Backup & Replication v13
or installing it for the first time, you may hit a roadblock: "Required port 443... is occupied by another application." In v13, port 443 is hardcoded for the Veeam Web Service/API Gateway
This conflict typically occurs because another service is already using the default HTTPS port on your backup server. Here is how to identify and resolve the conflict. 1. Identify the Conflict To find out which application is blocking Veeam, use the Command Prompt (run as Administrator): Find the Process ID (PID):
Run the following command to see what is listening on port 443: netstat -ano | findstr :443 Use code with caution. Copied to clipboard Locate the Application: Note the PID in the far-right column (e.g., ). Use this command to see the application name: tasklist /FI "PID eq [YOUR_PID]" Use code with caution. Copied to clipboard Alternative: Task Manager , go to the tab, and sort by PID. 2. Common Culprits Several services frequently "park" on port 443: Hyper-V Replication: If your VBR server also acts as a Hyper-V Replica server, it may be using 443. IIS (Internet Information Services):
Web servers or management consoles (like WSUS or a local website) often bind to 443. VisualSVN or Apache: Other web-based management tools. 3. How to Resolve Since Veeam v13 currently has no supported method
to change its own internal web service port during installation, you must move the application: For Hyper-V: Hyper-V Settings Replication Configuration Change the port from to another available port (e.g., Update your individual VM Replication settings to match. IIS Manager (InetMgr.exe) , right-click the conflicting site, and select Edit Bindings Change the HTTPS port from
or add a specific IP address binding to free up the port for Veeam. Temporary Workaround: Stop the conflicting service (e.g., net stop http
) to finish the Veeam installation, then re-evaluate the service's port requirements afterward. Do you need help checking if Hyper-V Replication is specifically causing the hold-up on your server?
Major Issues After Upgrading to Veeam V13: Port 443 Conflict
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:
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):
services.msc → locate service → Stop & set Startup type to Disabled.Case B – IIS with its default site:
iisreset /stop or disable the World Wide Web Publishing Service.Case C – Another legitimate service you need (e.g., SSRS):
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:
Prevention Tips for Future Deployments
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.
To resolve the error where port 443 is occupied, you must identify the conflicting application and either stop it or reconfigure it to use a different port. Starting with Veeam Backup & Replication (VBR) v13, port 443 is a hardcoded requirement for the REST/Web UI service, and there is no supported way to change it within Veeam itself. 1. Identify the Conflicting Application
Use the command line to find out which process is currently holding the port: Open Command Prompt as an Administrator. Fix: Veeam Port 443 Occupied by Another Application
Run Netstat: Type netstat -aon | findstr :443 and press Enter.
Note the PID: Look at the last column of the output for the Process ID (PID). Find the 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 IIS, SQL Reporting Services, or Hyper-V Replication. 2. Common Fixes for Specific Services
The error "Required port 443 for Veeam Backup & Replication is occupied by another application" is a classic collision between modern web-based services and Veeam's deep reliance on HTTPS for its core services. While intimidating at first glance, it is almost always resolvable by methodically identifying the offending process—most often IIS—and either moving it to a different port or eliminating it entirely.
Remember: Port 443 is a precious resource on any Windows server. Treat it as such, dedicate Veeam to its own machine wherever possible, and always perform a port audit before installation or upgrade. Your backups—and your peace of mind—depend on it.
Need further assistance? Visit the Veeam R&D Forums or contact Veeam Support with the output of veeam_backup_service.log and the results of your netstat analysis.
Required Port 443 for Veeam Backup & Replication is Occupied by Another Application: A Comprehensive Guide
Veeam Backup & Replication is a popular data backup and recovery solution used by many organizations to protect their critical data. However, during the installation or configuration process, users may encounter an error message indicating that the required port 443 for Veeam Backup & Replication is occupied by another application. In this article, we will explore the causes of this issue, its impact on Veeam Backup & Replication, and provide step-by-step instructions on how to resolve the problem.
What is Port 443 and Why is it Required for Veeam Backup & Replication?
Port 443 is the default port for HTTPS (Hypertext Transfer Protocol Secure) traffic. It is used for secure communication between web servers and clients. In the context of Veeam Backup & Replication, port 443 is used for communication between the Veeam Backup & Replication console and the Veeam services.
Veeam Backup & Replication uses port 443 for several purposes, including:
Causes of the "Required Port 443 for Veeam Backup & Replication is Occupied by Another Application" Error
The "required port 443 for Veeam Backup & Replication is occupied by another application" error occurs when another application or service is using port 443, preventing Veeam Backup & Replication from using it. This can happen due to various reasons, including:
Impact of the Error on Veeam Backup & Replication
If the required port 443 for Veeam Backup & Replication is occupied by another application, it can prevent Veeam Backup & Replication from functioning properly. This can lead to:
Resolving the "Required Port 443 for Veeam Backup & Replication is Occupied by Another Application" Error
To resolve the error, you need to identify the application or service occupying port 443 and either stop it or change its port usage. Here are the step-by-step instructions:
Method 1: Stop the Occupying Application or Service
Method 2: Change the Port Usage of the Occupying Application or Service
Method 3: Change the Veeam Backup & Replication Port
Conclusion
The "required port 443 for Veeam Backup & Replication is occupied by another application" error can prevent Veeam Backup & Replication from functioning properly, leading to failed backups, console connectivity issues, and data loss. By identifying the occupying application or service and either stopping it or changing its port usage, you can resolve the error and ensure that Veeam Backup & Replication functions correctly. If necessary, you can also change the Veeam Backup & Replication port to a different port. By following the steps outlined in this article, you can quickly resolve the issue and ensure the reliability and security of your backup infrastructure.
Fixing the "Port 443 Occupied" Error in Veeam Backup & Replication
If you’re attempting to install or upgrade to Veeam Backup & Replication v13, you may encounter a blocking error: "Required port 443 for Veeam Backup & Replication is occupied by another application." This happens because Veeam v13 now requires port 443 for its API Gateway and Web Service.
In many cases, port 443 is hardcoded in the installer, meaning you cannot simply choose a different port during the setup process. Step 1: Identify the Conflicting Application
Before you can proceed, you need to know which service is "squatting" on port 443.
Use PowerShell: Run the following command to find the Process ID (PID) using the port:Get-NetTCPConnection -LocalPort 443 | Select-Object LocalAddress, LocalPort, OwningProcess, State.
Use Command Prompt: Alternatively, run netstat -anob | findstr :443 to see the executable name directly. Common culprits include:
Windows Admin Center: Frequently uses 443 and may need to be uninstalled or moved to a different port.
Hyper-V Replication: If your backup server also acts as a Hyper-V replica host, it likely uses 443 for replication traffic.
VMware vCenter/ESXi: Often found in environments where management tools are co-located.
IIS (Internet Information Services): Default web sites or other web applications hosted on the same server. Step 2: Resolve the Conflict
Since Veeam v13’s use of port 443 is currently required for the installation to finish, you have two primary options:
Relocate the existing application: If possible, change the port of the conflicting software (e.g., move Windows Admin Center to port 6516).
Temporary Shutdown: Stop the conflicting service just long enough to complete the Veeam upgrade. However, be aware that Veeam may fail to function correctly after the upgrade if the other application reclaims the port. Step 3: Changing the Port Post-Installation
While the installer is rigid, some community experts suggest that you can attempt to change the port after the installation is successful. For other Veeam components like the Veeam Service Provider Console, ports can sometimes be modified via IIS Manager under Site Bindings.
Important Security Note: Avoid installing Veeam on a Domain Controller. While it might solve a port conflict, it significantly increases your ransomware risk by exposing your backup server to domain-level compromises. Title: Troubleshooting "Port 443 Required for Veeam Backup
This error typically occurs during an upgrade to Veeam Backup & Replication v13 or later, where port 443 is now hardcoded for the REST/Web UI service. Because this port is required and cannot be changed within Veeam's current supported configuration, you must identify and relocate the conflicting application. 1. Identify the Conflicting Application
The first step is to find out which process is "squatting" on port 443.
Using PowerShell (Recommended): Run the following command as an administrator to see the process name: powershell
Get-Process -Id (Get-NetTCPConnection -LocalPort 443).OwningProcess Use code with caution. Copied to clipboard
Using Command Prompt: Run netstat -aon | findstr :443 to find the PID (Process ID) in the far-right column. You can then match this PID in Task Manager under the "Details" tab. 2. Common Conflicts & Solutions Once identified, you usually have three paths forward: Veeam B&R 13 Change Web Service Port 443
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. "The port 443 required for Veeam Backup &
The Great Veeam Backup Debacle
It was a typical Monday morning for John, the IT administrator at a medium-sized company. He was sipping his coffee and checking his emails when he received a notification from his monitoring system about a critical issue with one of his Veeam Backup & Replication servers. The error message read:
"Required port 443 for Veeam Backup & Replication is occupied by another application."
John's heart sank. This was not good. Veeam Backup & Replication was his primary backup solution, and if it wasn't working, his company's data was at risk. He quickly opened the Veeam console to investigate the issue.
After a few minutes of digging, John discovered that the problem was indeed related to port 443, which was the default port used by Veeam Backup & Replication for communication between the backup server and the Veeam console. However, it seemed that another application had taken over the port, causing the conflict.
John checked the list of running processes on the server and found that a new application, called "Acme Secure Gateway", had been installed by a colleague a few days ago. The application was designed to provide secure access to the company's network, but it appeared to be using port 443, which was causing the conflict with Veeam.
John tried to stop the Acme Secure Gateway service, but it wouldn't budge. He then tried to change the port used by Veeam Backup & Replication to a different one, but that would require updating the configuration on multiple servers, which would take some time.
As John was trying to troubleshoot the issue, his phone started ringing. The company's CEO was on the line, asking about a critical server that was supposed to be backed up the previous night. John explained the situation, and the CEO stressed the importance of getting the backups up and running as soon as possible.
With the pressure on, John decided to take a more drastic approach. He temporarily stopped the Acme Secure Gateway service and changed the port used by Veeam Backup & Replication to a different one. He then restarted the Veeam services and tested the backups.
To his relief, the backups started working again, and the CEO was happy to hear that the critical server had been backed up successfully. However, John knew that he needed to find a more permanent solution to avoid similar conflicts in the future.
After some discussion with the team, they decided to move the Acme Secure Gateway to a different server and change its configuration to use a different port. They also updated the Veeam configuration to use a new port, and everything was back to normal.
John breathed a sigh of relief, happy that he had resolved the issue before it caused any major problems. He made a mental note to double-check the configuration of new applications before they were deployed, to avoid similar conflicts in the future.
The End
When upgrading to Veeam Backup & Replication (VBR) v13 , many users encounter a critical installation block:
"Required port 443 for Veeam Backup & Replication is occupied by another application" In version 13, port 443 is
for the Veeam Web Service/API Gateway. This requirement is strictly enforced by the installer's compatibility check, and there is currently no supported way to change this port within Veeam or bypass the check. Identifying the Conflict
To resolve the block, you must identify which non-Veeam service is listening on port 443. Diagnostic Command netstat -anob
in an elevated Command Prompt to see which Process ID (PID) and executable are using the port. Common Culprits Hyper-V Replication
: If your VBR server also acts as a Hyper-V Replica server, it may be using 443 for replication traffic. IIS / Web Servers : Existing web hosting services or management consoles. Security Agents : Third-party monitoring or security software. How to Resolve the Block
Since Veeam's port 443 requirement is mandatory for v13, the solution involves reconfiguring the application: Reconfigure Hyper-V Replication Navigate to Hyper-V Settings Replication Configuration Change the listening port from to an alternative (e.g., 444).
Update the Replica settings for each individual VM to match this new port to avoid re-replication. Adjust Third-Party Applications
If a third-party service allows it, reconfigure it to use a different HTTPS port (e.g., 8443 or 9443). Temporary Disabling
Some admins report success by temporarily stopping the conflicting service to complete the Veeam upgrade. However, the Veeam Web Service may fail to start afterward if the original application resumes control of port 443. Dedicated Infrastructure
Veeam experts recommend moving the backup server to a dedicated, non-domain-joined environment to avoid conflicts and improve security.
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.
To understand the error, one must first appreciate that Veeam Backup & Replication is not just a file-copy tool—it is a distributed, web-centric platform. Port 443 is the default port for:
When you install Veeam Backup & Replication (version 10, 11, 12, or later), the installer attempts to bind the Veeam Backup Service to port TCP 443 on the local machine. If any other process has already claimed that port—even if it's just listening and not actively serving traffic—Veeam will refuse to start or install.
One of the most common installation and runtime errors encountered with Veeam Backup & Replication is the notification: "Required port 443 for Veeam Backup & Replication is occupied by another application."
Port 443 is the standard TCP port used for HTTPS (secure web traffic). Veeam requires this port for various components—most notably the Veeam Backup Enterprise Manager and the Veeam Backup Service on the backup repository—to enable secure communication between the console, the server, and managed agents.
Because Port 443 is the default port for secure web traffic worldwide, it is frequently claimed by other applications (like IIS, WSUS, or third-party web servers), leading to a binding failure during Veeam installation or service startup.
If Veeam is installed on an Exchange Server (not recommended but sometimes done in small environments), Exchange’s front-end services (Outlook Web App, ECP, ActiveSync) listen on port 443.
This is the most common fix.
inetmgr).https entry for port 443 and click Edit.8443 (or 4443).iisreset from command line.Alternatively, if you don’t need the default website at all, stop and disable it:
Stop-Website 'Default Web Site'
Set-ItemProperty 'IIS:\Sites\Default Web Site' -Name ServerAutoStart -Value $false
Now restart Veeam Backup Service.