Type cmd , right-click , and select Run as administrator . Type the following command and press Enter : netstat -ano | findstr :443 Use code with caution.
Right-click the button and select Terminal (Admin) or PowerShell (Admin) .
Reconfigure the web server configuration file ( .conf ) to listen on a custom port. tomcat.exe Third-party management tools or print servers Modify Tomcat's server.xml connector port string. Step 2: Resolving the Conflict Type cmd , right-click , and select Run as administrator
When upgrading to Veeam Backup & Replication (VBR) v13 is a strictly required, hardcoded dependency for the new Veeam Web Service/API Gateway
Change the port value to an alternate port (such as 8443 ), or apply a explicit host header name if sharing an IP address. Click and restart IIS. Scenario C: Transient or Non-Essential Applications Reconfigure the web server configuration file (
: Existing corporate websites, WSUS administration consoles, or local intranet applications hosting secure traffic.
: If port 443 is occupied, the Veeam installer will typically block upgrades from v12 to v13 until the conflict is resolved. Click and restart IIS
sc query W3SVC
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
If your VBR server is also a Hyper-V host, change the replication port. Go to > Replication Configuration and change the port from 443 to a different value.
: In some environments, WinRM or WS-Management may occupy this port Temporarily stop the Windows Remote Management