How to Change the Veeam Reverse Proxy Service Port (443) After Deployment

7. Restart the Veeam Backup Server so that every Veeam service starts with the new port. Restarting only the Veeam Reverse Proxy Service, or only the Veeam Backup Service, is not sufficient, because all Veeam services must use the new port.

Non-Elevated Consoles

A console that is started without elevation cannot read the port from either the local appsettings.json file or the ReverseProxyCustomPort value under HKEY_LOCAL_MACHINE, and continues to connect to port 443. For users who run the console without elevation, use one of the following:

• Run the Veeam Backup & Replication Console as an administrator.
• Specify the port explicitly when connecting, in the host:port format.
• Create the ReverseProxyCustomPort value under HKEY_CURRENT_USER\SOFTWARE\Veeam\Veeam Backup and Replication\ instead of the HKEY_LOCAL_MACHINE location.

The change can also be confirmed in the following log:
C:\ProgramData\Veeam\ReverseProxy\Logs\service.log

After the restart, the listeners are bound to the new port:

[INF]   Now listening on: https://localhost:8443
[INF]   Now listening on: https://[::]:8443

Known Issue: Veeam Backup Enterprise Manager Loses Its Connection to the Backup Server

Issue Summary

After the port is changed, Veeam Backup Enterprise Manager continues to connect to the Veeam Backup Server on the previous port. The port cannot be updated by editing the backup server in the Enterprise Manager web UI. The failed connection is recorded in the Svc.VeeamBES.log file, as shown in the following example:

[CGrpcVbSrvServiceProxy] Connecting by certificate to VBR's [vbr.domain.tld] grpc port [443]. New remoting client id generated:
Updating licensed instances group ids
Unable to connect by gRPC to host [vbr.domain.tld]
No connection could be made because the target machine actively refused it.

Resolution

To restore the connection:

1. Remove the backup server from Enterprise Manager.
2. Add it again, specifying the new port.
   _{Note: Re-adding a backup server can create duplicate entries in the Enterprise Manager database. The duplicate entries are temporary.}

This behavior will be improved in a future version to allow the port used to connect to the Veeam Backup Server to be modified.

Known Issue: Veeam Updater Connection Errors

Issue Summary

When the Primary service port has been changed, host discovery (a rescan of the Veeam Backup Server) and Update Settings Synchronization continue to connect to the Veeam Updater service on port 443. As a result, the following error occurs:

Failed to connect to the Veeam Updater service
No connection could be made because the target machine actively refused it.
(hostname:443)

While this error occurs, the Veeam Updater service may be unable to retrieve licensing information and discover available updates.

Resolution

This issue was resolved starting in Veeam Backup & Replication 13.1.2.

Known Issue: Veeam Service Provider Console Cannot Connect to the Backup Server

Issue Summary

In Veeam Service Provider Console 9.2 and older, connections to a Veeam Backup Server are always made using port 443. When the Primary service port has been changed, the following operations fail:

• Adding the backup server as a Cloud Connect server or as a hosted backup server fails with the error Backup services are not responding or not running, although all Veeam services are running.
• Opening a wizard that is redirected from Veeam Service Provider Console for a managed backup server fails with the error Failed to load the backup server plugin. Refresh the page and try again.
• Opening the backup server web UI using Open Web UI fails with the error Target product's (Vbr) UI is inaccessible.

Resolution

This issue was resolved starting in Veeam Service Provider Console 9.3, now the configured port will be used appropriately.