Web servers or Microsoft-related services like SQL Reporting Services often bind to this port. Other Web Servers:
Match the PID found in the steps above to the list under the Details tab to see the application's name and location . Common Conflicts and Fixes The most frequent culprits for this conflict include: Veeam B&R 13 Change Web Service Port 443 Web servers or Microsoft-related services like SQL Reporting
Reviewers on the Veeam R&D Forums have noted that stopping the service entirely may be necessary if it prevents the console from loading. Next Steps Next Steps | Application / Service | Typical
| Application / Service | Typical Use Case | | :--- | :--- | | | Default Web Site, WSUS, or any internal web app. | | Microsoft SQL Server Reporting Services (SSRS) | Uses HTTP.SYS to listen on Port 443 for reports. | | Skype for Business / Teams | Can bind to ports unexpectedly. | | Remote Desktop Gateway (RD Gateway) | Uses HTTPS (443) for secure RDP connections. | | Syslog / SIEM agents | Some agents redirect SSL traffic via 443. | | Antivirus Web Filtering | Symantec, McAfee, or Cisco AMP can proxy HTTPS. | | Hyper-V Host Service | Certain Hyper-V configurations use port 443 for management. | | Docker Desktop (Windows containers) | The MobyLinuxVM engine may bind to 443. | | Previous Veeam Installation | Leftover services from a failed uninstall. | | | Remote Desktop Gateway (RD Gateway) |
: The installer performs a pre-install check; if 443 is in use, the "Required port 443 is occupied by another application" error triggers Common Conflicting Applications Hyper-V Replication : Often uses 443 for HTTPS replication traffic IIS (Internet Information Services)
: Sometimes causes conflicts that prevent the VBR console from loading.