Configure edge routing rules or network address translation rules to map incoming traffic to alternative destinations.
If you are upgrading from Veeam v12 to v13 and have no alternative, you can temporarily disable the conflicting service to allow the upgrade to complete:
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.
Major Issues After Upgrading to Veeam V13: Port 443 Conflict Configure edge routing rules or network address translation
If you have a converged environment where your Veeam server is also a Hyper-V replica server, you will need to change the replication port. Open the on your host. Right-click the Hyper-V host and select Hyper-V Settings . Go to the Replication Configuration tab.
Is this a Veeam server or is it managed by a Service Provider (VSPC)?
Look for rows showing LISTENING . The number at the far right of that row is the . Use PowerShell If you share with third parties, their policies apply
Here are some common causes of port 443 being occupied:
Example output:
Here is a step-by-step technical guide to identify the offending application and free up port 443 for Veeam. Step 1: Identify the Occupying Application Major Issues After Upgrading to Veeam V13: Port
Note: You must also update the VM replica settings on your primary hosts to point to the new port so replication traffic continues flowing uninterrupted. Scenario B: Microsoft IIS (Internet Information Services)
You will see an output similar to:
Is Veeam installed on a or a shared server?
: 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.
You need to discover exactly which process ID (PID) and executable is occupying port 443. Open or Command Prompt as an Administrator.