Required Port 443 For Veeam Backup & Replication | Is Occupied By Another Application [hot]

: If your backup server also acts as a Hyper-V replica host, it likely uses 443 for replication traffic.

The default Windows web server often claims 443 for the Default Web Site.

: Before installing or upgrading, run an administrative netstat -ab command and document which critical ports (including 80, 443, 135, 445) are already in use and by which applications. : If your backup server also acts as

If the command returns no output (or only shows Veeam services starting up), the port is successfully cleared.

Get-NetTCPConnection -LocalPort 443 | Select-Object -Property LocalAddress, LocalPort, State, OwningProcess Get-Process -Id (Get-NetTCPConnection -LocalPort 443).OwningProcess If the command returns no output (or only

Example output:

To avoid running into these issues in the future, follow these industry best practices: If you cannot change the port of the

Use the command line to find which process is holding the port: Open Command Prompt as Administrator. netstat -ano | findstr :443 (Process ID) at the end of the line.

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.

This error is a common blocker when upgrading to or installing Veeam Backup & Replication v13 port 443 is now hardcoded and required for the Veeam Web Service and API Gateway

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