The most reliable solution is to follow Veeam's recommendation: "we do not expect the backup server to be shared with 3rd party apps as that commonly leads to unpredictable behavior". Ideally, dedicate a server exclusively to Veeam Backup & Replication.
I can provide tailored to your exact environment. SQL restore using explorer - Veeam R&D Forums
By following these steps and considerations, you should be able to resolve the issue of port 443 being occupied by another application when trying to use it for Veeam Backup replication. The most reliable solution is to follow Veeam's
Port 443 is the default port used for HTTPS (Hypertext Transfer Protocol Secure) communication. Veeam Backup & Replication uses this port to establish a secure connection between the backup server and the vCenter server or ESXi hosts for replication and backup operations. When Veeam Backup & Replication is configured to use port 443, it attempts to establish a secure connection to the target server. However, if another application is using port 443, the Veeam Backup & Replication job will fail.
This will list all URL reservations. Look for something like: http://+:443/ or https://+:443/ reserved for a specific user or service group (e.g., NT SERVICE\SSRS ). SQL restore using explorer - Veeam R&D Forums
: Run the following command as an Administrator: Get-Process -Id (Get-NetTCPConnection -LocalPort 443).OwningProcess
: Always install Veeam Backup & Replication on a dedicated server. Avoid co-hosting it with web servers, domain controllers, or database servers. When Veeam Backup & Replication is configured to
: Standard web servers or other management consoles frequently bind to this port SQL Server Reporting Services : May be configured to use 443 for web access. Other Monitoring Tools
When you try to configure Veeam Backup replication, you may encounter an error message indicating that port 443 is already in use by another application. This can be frustrating, especially if you're not aware of what application is using the port.
Sometimes, netstat shows that the "System" process is listening on 443, but IIS is not installed. This is often caused by listening on port 443 for HTTPS listeners.