netstat -ano shows PID 5678 listening on 443 → tasklist /fi "PID eq 5678" returns w3wp.exe (IIS).
The Veeam Backup Enterprise Manager and modern Veeam consoles communicate via this port. Step 1: Identify the Conflicting Application
Connecting the backup server to VMware vCenter Servers or ESXi hosts. netstat -ano shows PID 5678 listening on 443
For any existing VMs replicating to this host, update their individual replica server port properties to match. Culprit C: VMware Workstation or Third-Party Web Servers
Which of Veeam Backup & Replication are you currently running? For any existing VMs replicating to this host,
Secure API calls to public cloud platforms.
This guide provides a step-by-step walkthrough to identify the conflicting application and free up Port 443 so your Veeam infrastructure can run smoothly. Step 1: Identify the Conflicting Application This guide provides a step-by-step walkthrough to identify
user wants a long article about the error "required port 443 for veeam backup & replication is occupied by another application". I need to provide comprehensive troubleshooting steps. I'll search for information on the error, its causes, and solutions, including using Veeam's ports configuration tool, identifying conflicts, and manual resolution. search results show various topics but not a direct match for the specific error. I need to find more specific information. Let's search for the exact error phrase. search results don't show the specific error. Maybe the error is from the Veeam installer. Let's search for "Veeam Backup & Replication setup port 443 occupied". search results show a Veeam Community post about Veeam B&R 13 and port 443. This seems relevant. I should open it. is a very relevant thread. It mentions that port 443 is hardcoded for the Veeam Web Service/API Gateway in v13 and newer, and there's no supported way to change it. The error likely occurs during installation or upgrade when something else is using port 443. I should also search for general information on Veeam port usage and conflicts. should also search for Veeam KB articles related to port conflicts. search results include a Veeam Community post about Veeam B&R 13 and port 443. This seems relevant. I should open it. discussion mentions that port 443 is hardcoded for the Veeam Web Service/API Gateway in version 13 and newer, and there's no supported way to change it. It also mentions that the issue can occur during upgrades. There's also a mention of PID 4 blocking the port. I'll also search for solutions related to changing the port for Veeam components, and for tools like VeeamPortsConfigurationEditor . search results show some general information, but not a specific fix. I'll use the Veeam community thread as a primary source. I'll also look for information on Veeam's port usage and how to identify the process using port 443. Now, I need to write a comprehensive article. The article should cover the error message, causes, identification of the conflicting application, solutions (including temporary disabling, reconfiguring the conflicting app, and Veeam-specific configuration changes), and prevention best practices. I'll structure the article with an introduction, sections on understanding the error, identifying the culprit, resolution steps, advanced troubleshooting, best practices, and a conclusion. I'll cite the Veeam community thread, port usage documentation, and netstat commands.'ll also look for information on Veeam's port usage for version 13. search results show a Veeam Community post about Veeam B&R 13 and port 443. This is the most relevant source. I'll also need to provide instructions on identifying the process using port 443. I'll search for that as well.'ll use the information from the Veeam Community post and general port-checking methods. Now I need to write the article. I'll structure it as follows:
Open IIS Manager, expand your site, click Bindings in the right-hand Actions panel, select the HTTPS binding, edit it, and change port 443 to something else (e.g., 8443 ).
If you need the conflicting application to remain active, change its HTTPS port to something else (like 4443 or 8443) to leave 443 open for Veeam.
Run netstat before installing Veeam to ensure ports 443, 6160, 9392, and 11560 are completely free.