John checked the list of running processes on the server and found that a new application, called "Acme Secure Gateway", had been installed by a colleague a few days ago. The application was designed to provide secure access to the company's network, but it appeared to be using port 443, which was causing the conflict with Veeam.
Based on the identified process:
Use the command line to find out which process is currently holding the port: as an Administrator. John checked the list of running processes on
: If your VBR server is also a Hyper-V host with replication enabled, it often claims 443. called "Acme Secure Gateway"
You’re installing or upgrading Veeam Backup & Replication, and suddenly you hit a roadblock: and suddenly you hit a roadblock: