Attempt to connect to the localhost server to confirm authentication succeeds.
: In some cases, the WinRM service or WS-Management must be stopped to allow the Veeam console to load correctly. Option B: Temporary Stop for Upgrade Veeam B&R 13 Change Web Service Port 443
Can the conflicting application be ? Share public link Attempt to connect to the localhost server to
Older desktop versions famously utilized port 443 as a fallback for incoming connections.
Port 443 is the default port for HTTPS web traffic. Veeam uses this port for several vital functions: communication between the backup server and vCenter Server/ESXi hosts, communication with cloud repositories, and for the Veeam Guest Catalog service. In version 13, Veeam introduced the "Veeam Web Service" and API Gateway, which during installation and for normal operation. This service handles REST API requests and modern web-based management interfaces. The installer blocks the upgrade process when it detects another service already listening on this port. The error essentially means Veeam is unable to bind to the port it needs to operate, which halts the installation or upgrade process. Share public link Older desktop versions famously utilized
If the Veeam server is intended to be a dedicated backup appliance and IIS or other web services were installed accidentally or are not needed:
Apache, Nginx, or XAMPP installed on the backup server. 🚀 Step 2: Resolving the Conflict In version 13, Veeam introduced the "Veeam Web
The offender. On Windows Server, the default IIS installation automatically creates a "Default Web Site" bound to all unassigned IP addresses on port 80 (HTTP) and, critically, port 443 (HTTPS) . Even if you don't run a public website, this default binding claims port 443.