Required Port 443 For Veeam Backup & Replication Is Occupied By Another Application Jun 2026

Never install Veeam Backup & Replication on a machine running IIS, Active Directory, or vCenter. Keep the backup server dedicated.

If the software was already upgraded but the web service crashed, navigate to Windows Services ( services.msc ) and manually start the Veeam Backup REST Service ( VeeamBackupRESTSvc ). Summary of Alternative Setup Strategy

Are you currently ?

Veeam's decision to hard-code port 443 for the new web service and API gateway was intentional to address security concerns, aiming to prevent the backup server from hosting other publicly exposed services. This approach, however, has impacted: Never install Veeam Backup & Replication on a

TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 1234 TCP [::]:443 [::]:0 LISTENING 1234

If Microsoft IIS is running on the backup server, it may be holding a broad binding across all IP addresses on port 443. Open the .

Veeam Backup & Replication (VBR) v13 is a mandatory, hardcoded requirement for the new Veeam Web Service/API Gateway Summary of Alternative Setup Strategy Are you currently

Before changing any settings, you must identify the exact Process Identifier (PID) and the name of the software that has seized the port. Open or Command Prompt as an Administrator.

Older desktop versions famously utilized port 443 as a fallback for incoming connections.

With the pressure on, John decided to take a more drastic approach. He temporarily stopped the Acme Secure Gateway service and changed the port used by Veeam Backup & Replication to a different one. He then restarted the Veeam services and tested the backups. Open the

Once you have determined the best path forward, execute these final actions to allow Veeam to complete its deployment or service initiation:

John tried to stop the Acme Secure Gateway service, but it wouldn't budge. He then tried to change the port used by Veeam Backup & Replication to a different one, but that would require updating the configuration on multiple servers, which would take some time.

Open the IIS Manager, select the website under the "Sites" tree, click Bindings in the right-hand Actions panel, edit the HTTPS binding, and change the port from 443 to something else.