This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Required Port 443 For Veeam | Backup & Replication Is Occupied By Another Application
Now, find which application owns that PID:
tasklist | findstr 4588 Or, in PowerShell: Now, find which application owns that PID: tasklist
Run netstat -aon | findstr :443 one more time. Now you should see the Veeam services (like VeeamBackupSvc ) happily listening on port 443. You know port 443 is the lifeblood of
Your heart sinks. You know port 443 is the lifeblood of Veeam’s communication (encrypted traffic between the backup server, hosts, and guest interaction proxies). Without it, your backup jobs are dead in the water. netstat -aon | findstr :443 You will see
The magic number here is the (Process ID)—in this case, 4588 .
netstat -aon | findstr :443 You will see output similar to this: TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 4588
A Veeam server should ideally be a dedicated machine. If you’re constantly fighting for ports, consider moving Veeam to its own physical or virtual server where nothing else runs on ports 80, 443, or 9392 (the Veeam console port). Have you run into a different process hogging port 443? Mention it in the comments below—let’s crowdsource a full list of offenders!