Required Port 443 For Veeam Backup Replication Is Occupied By Another Application Link ((link)) Online

Once you have stopped the conflicting application or reassigned the port, restart the Veeam services: Open services.msc . Locate . Right-click and select Restart .

: Run the following command as an Administrator: Get-Process -Id (Get-NetTCPConnection -LocalPort 443).OwningProcess

: Launch the Veeam Backup & Replication upgrade or setup wizard. The compatibility verification step will pass smoothly. Once you have stopped the conflicting application or

Select your site under the Connections tree, and click in the right-hand panel.

System administrators upgrading or installing face an blocker where the installation wizard or the core services fail to start. The blocking error indicates that TCP Port 443 is already in use by another software process on the backup server. : Run the following command as an Administrator:

Update the in each VM's replication settings to match the new port to avoid re-replicating data. Stop and Disable Conflicting Services :

This error typically presents during installation, component upgrades, or when pushing agent updates, halting the process and requiring immediate resolution. Why Veeam Needs Port 443 or when pushing agent updates

: If the host server acts as a Hyper-V Replication target over HTTPS, the system listener binds directly to port 443.

Historically, Veeam used port 9392 for its internal backup service communication. However, starting with , Veeam shifted to a secure modern web architecture featuring an embedded REST API Gateway and an upgraded web management service.