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

After freeing port 443:

  • Check Veeam event logs (Event Viewer → Applications and Services Logs → Veeam Backup).

    • netstat -ano | findstr :443

    Example output:

    TCP    0.0.0.0:443           0.0.0.0:0              LISTENING       1234

    The number 1234 is the Process ID (PID).

    In some environments, Port 443 is a business-critical endpoint for a public-facing web server or reverse proxy. Reconfiguring that application may be impossible.

    Veeam allows you to change its default ports (with caveats).

    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 After freeing port 443:

    Resolving Port 443 Conflicts in Veeam Backup & Replication Veeam Backup & Replication is the backbone of many disaster recovery strategies, but its installation or operation can come to a screeching halt when a "Port 443 occupied" error appears. Because Port 443 is the industry standard for HTTPS traffic, it is highly contested by web servers, monitoring tools, and communication platforms.

    If you are seeing errors indicating that required port 443 for Veeam Backup & Replication is occupied by another application, this guide will help you identify the culprit and clear the path for your backups. Why Veeam Needs Port 443 Veeam uses Port 443 for several critical functions:

    RESTful API Service: Modern Veeam components communicate via HTTPS.

    Cloud Connect: Securely transmitting data to service providers.

    vSphere Integration: Communicating with VMware vCenter or ESXi hosts.

    Veeam Backup Enterprise Manager: Providing the web-based management interface.

    When another service grabs this port first, Veeam cannot bind its services, leading to failed installations or "Service Unreachable" errors. Step 1: Identify the "Occupying" Application

    Before you can fix the conflict, you need to know what is sitting on the port. Open PowerShell or Command Prompt as an Administrator.

    Run the following command to find the Process ID (PID) using Port 443: powershell netstat -ano | findstr :443 Use code with caution.

    Look for the line that says LISTENING. The number at the far right is the PID. To see which application owns that PID, run: powershell tasklist /fi "pid eq [YOUR_PID_HERE]" Use code with caution. Common Culprits

    IIS (Internet Information Services): Often used for other web applications on the same server.

    VMware Workstation/Player: The "VMware Host Agent" often claims 443.

    Skype/Teams: Older versions of communication tools sometimes default to 443.

    Antivirus/EDR Agents: Some security consoles use 443 for local communication. Step 2: Resolve the Conflict Check Veeam event logs (Event Viewer → Applications

    You have three primary ways to fix this, depending on your environment. Option A: Disable or Move the Conflicting Service

    If the application occupying the port isn't vital to that specific server, the easiest fix is to stop it.

    For IIS: Change the "Default Web Site" binding from 443 to another port (like 4443) via the IIS Manager.

    For VMware Workstation: Go to Edit > Preferences > Shared VMs and change the port or disable sharing. Option B: Change Veeam’s Default Port

    If you are performing a fresh installation, Veeam allows you to specify the ports. If the system is already installed, changing the port is more complex and involves the registry or the Veeam Configuration backend.

    Warning: Changing Veeam's default ports may require you to update firewall rules and re-authenticate connected components. Option C: Use a Dedicated Backup Server

    Best practice dictates that a Veeam Backup Management Server should ideally be a dedicated role. If your server is acting as a Web Server (IIS), a Print Server, and a Backup Server, port conflicts are inevitable. Moving Veeam to its own VM or a dedicated physical box eliminates this issue entirely. Step 3: Verify the Fix

    Once you have stopped the conflicting application or reassigned the port, restart the Veeam services: Open services.msc. Locate Veeam Backup Service. Right-click and select Restart.

    Check the netstat -ano | findstr :443 command again to ensure the Veeam PID is now the one listening.

    The "Port 443 occupied" error is a common networking hurdle, not a flaw in the Veeam software. By identifying the PID using netstat and either relocating that application or dedicating the server to Veeam, you can ensure your data protection environment remains stable and secure.

    Veeam Backup & Replication v13 is a hardcoded requirement for the Veeam Web Service/API Gateway

    . If this port is occupied by another application, the Veeam services will fail to bind, and the application will not start. Veeam Community Resource Hub Common Applications Occupying Port 443 Hyper-V Replication

    : If your backup server also acts as a Hyper-V replica server, it often reserves port 443. IIS (Internet Information Services)

    : Other web applications or management portals may be bound to the default HTTPS port. Windows Remote Management (WinRM) netstat -ano | findstr :443

    : Sometimes conflicts with Veeam's ability to load its console. How to Resolve the Conflict Since port 443 is

    and cannot be changed within Veeam v13 itself, you must reconfigure the conflicting application instead. Veeam Community Resource Hub Identify the Occupying Process Open PowerShell as an Administrator. netstat -anob | findstr :443 to find the Process ID (PID) using the port. Match the PID in Task Manager to find the specific software. Reconfigure Hyper-V (If applicable) Hyper-V Settings Replication Configuration Change the specified port from to an alternative (e.g., 444).

    Update individual VM replication settings to match the new port. Temporary Workaround for Upgrades

    Stop the conflicting service (e.g., IIS or Hyper-V Replication) before starting the Veeam upgrade.

    Once the upgrade completes, you may attempt to re-enable the third-party service on a different port. Registry Fix (Veeam Agents only) For standalone Veeam Agents

    (not the main VBR server), you can sometimes force a specific port via the registry key mentioned in Veeam KB2332 For further official guidance, refer to the Veeam Help Center used ports

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

    Step 1: Hyper-V Setting -> Replication Configuration -> Change Specify the Port from 443 to something else. Veeam B&R 13 Change Web Service Port 443 21 Nov 2025 —

    sc query W3SVC

    If running, you will see STATE : RUNNING.

    net stop W3SVC
sc config W3SVC start= disabled

    Then restart the Veeam Backup Service:

    net stop VeeamBackupSvc
net start VeeamBackupSvc

    Sometimes the installer thinks port 443 is occupied due to a stale socket or Windows HTTP API reservation. Check with:

    netsh http show urlacl
netsh http show servicestate

    You can remove a reservation with:

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

    Use caution – only delete what you recognize.