Required Port 443 For Veeam — Backup & Replication Is Occupied By Another Application ~upd~
The error occurs because Veeam Backup & Replication (VBR) mandates exclusive use of TCP Port 443 for its REST API Gateway and Web UI components . Starting with VBR v13, this port requirement is hardcoded during both fresh installations and in-place upgrades. If another web server, replication service, or security tool is already listening on HTTPS port 443, the Veeam installer will halt or the VeeamBackupRESTSvc service will fail to bind and refuse to start.
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.
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.
Major Issues After Upgrading to Veeam V13: Port 443 Conflict
If this error appears during a fresh installation or upgrade wizard: The error occurs because Veeam Backup & Replication
in an elevated Command Prompt to see which Process ID (PID) and executable are using the port. Common Culprits Hyper-V Replication
First, we need to find out what is currently using port 443. To do this, follow these steps:
: Before restarting your other application, modify its settings to listen on a non-standard port (e.g., port 4443 or 8443).
: If your backup server also acts as a Hyper-V replica host, it likely uses 443 for replication traffic. John's heart sank
User experience flow (concise)
: If you are running a single-server SOHO environment, read the release notes thoroughly. The v13 upgrade path might require significant changes to your infrastructure. Do not assume an in-place upgrade will be seamless.
: Open Task Manager ( Ctrl + Shift + Esc ), go to the "Details" tab, and sort by the "PID" column. Find the PID you noted from the netstat output. The corresponding "Name" column will tell you the executable file (e.g., svchost.exe , Skype.exe , httpd.exe ). This executable is the application conflicting with Veeam. If the process is svchost.exe , you may need to inspect the services running under that host to pinpoint the exact culprit.
If no other solution works and the conflicting application is critical and cannot be moved, the most straightforward path is to redeploy Veeam on a dedicated server or a virtual machine. This is considered a for Veeam Backup & Replication and will completely eliminate these types of port conflicts. He quickly opened the Veeam console to investigate the issue
Total: 90 minutes
The most frequent culprits on Windows Servers are often built-in Microsoft services:
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