Update the replica server port in the settings of each VM to match this new port.
Use caution – only delete what you recognize.
Stop the conflicting service (e.g., IIS or a custom web app). Complete the Veeam VBR v13 upgrade or installation.
: A frequent cause is the Hyper-V Replica service on the same server. An "easy fix" reported in Veeam R&D Forums involves changing the Hyper-V replication port from 443 to another value (e.g., 444) before proceeding with the Veeam upgrade.
Look for rows showing LISTENING . The number at the far right of that row is the . Use PowerShell Update the replica server port in the settings
In VBR v13, port 443 is for the API Gateway and Web service; there is currently no supported way to change this within the Veeam configuration itself. Therefore, you must move the other application to a different port. For Hyper-V Replication Servers : Navigate to Hyper-V Settings > Replication Configuration .
: Stop the conflicting service long enough to complete the Veeam upgrade. Permanent Fix :
Consult the Veeam Ports Guide to ensure no other required ports are blocked.
Before stopping services, you must identify what is using port 443. Open a Command Prompt or PowerShell as Administrator and run the following command: netstat -ano | findstr :443 Use code with caution. Complete the Veeam VBR v13 upgrade or installation
: Open a command prompt as administrator and run netstat -anob | findstr :443 . This will display the Process ID (PID) and the name of the executable using the port.
What did the netstat command reveal as the culprit?
For deeper connectivity troubleshooting, you can refer to the Veeam Ports Finder Tool to map out all required communications.
Veeam allows you to (with caveats).
You have three primary methods to free up the port for Veeam. Method A: Stop or Reconfigure the Competing Service
Then restart the Veeam Backup Service:
Open services.msc and look for:
: Veeam usually creates its own firewall rules, but you must ensure no external network firewalls are blocking 443 communication between the backup server and its components PowerShell commands to identify exactly which process is holding that port? Look for rows showing LISTENING