Highlight the https binding entry running on port 443 and click .
To avoid port conflicts in production environments, implement these infrastructure habits:
Your action plan must be based on the outcome of your investigation.
| Application / Service | Typical Context | |----------------------|------------------| | | 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. |
: VBR v13 introduces a mandatory web interface and API gateway that listens specifically on port 443 Licensing & Updates Highlight the https binding entry running on port
Before you can fix the issue, you must determine which application is currently listening on port 443. You can do this via the Command Line or PowerShell.
Because VBR includes web components (like the RESTful API or Enterprise Manager), IIS often claims port 443 for its default web bindings.
The appropriate solution depends on which application is occupying port 443 and your specific environment.
: Open a command prompt as an administrator and run: netstat -ano | findstr :443 | | Microsoft Exchange Server | Uses port
If you are seeing this error during an upgrade, it is strongly advised to plan for a brief downtime to allow the new web service to bind correctly.
After freeing up Port 443, restart your Veeam infrastructure services to allow Veeam to successfully bind to the port. Open ( services.msc ). Scroll down to the Veeam entries.
: Run a netstat check on target Windows servers prior to installing Veeam to ensure all required ports (443, 9392, 6160) are completely clear.
Windows Server often enables IIS by default, which claims ports 80 and 443. | | VMware vCenter Server (embedded) | If
For now, while Veeam product leadership has indicated a future intention to make the port configurable in VBR depending on demand, the present reality is that port 443 is a hard requirement for the newest versions. This guide provides you with the strategies you need to navigate that requirement and restore a stable, conflict-free data protection environment.
If the PID belongs to w3wp.exe or the system process handles it via IIS: Open ( services.msc ). Locate World Wide Web Publishing Service . Right-click it and select Properties . Change the Startup type to Disabled and click Stop . Method B: Change the Conflicting Application's Port
Select your site under the Connections tree, and click in the right-hand panel.
Look at the lines indicating a LISTENING state. The number at the far right of the output is the . To identify the application name by its PID, run: tasklist /FI "PID eq " Use code with caution. Common Culprits in Veeam Environments