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

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): Fix: Veeam Port 443 Occupied by Another Application

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 Phase 3: Resolve the Conflict Based on the

) 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

7. Example Case Resolution

Symptom: Veeam Backup Service fails to start. Event log shows “Address already in use:443”. go to the tab

Diagnosis: netstat -ano shows PID 5678 listening on 443 → tasklist /fi "PID eq 5678" returns w3wp.exe (IIS).

Action: Opened IIS Manager → Default Web Site → Bindings → removed HTTPS:443 binding → Restarted IIS (iisreset).
Result: Veeam Backup Service started normally.

Phase 3: Resolve the Conflict

Based on the identified process:

Phase 1: Identify the Conflicting Process

Do not guess. Use Windows built-in tools:

Common pitfalls (for graders to watch)