Change the Base URL or Listen Port

The configuration file for your Hub installation has two properties that determine where the service is accessible over the internet or internal network.

There are various reasons for wanting to change the base URL or listen port for your Hub installation. This can include domain or hosting migrations, rebranding, renaming, or security and access control.

Changing the listen port can be required for security purposes, load balancing, resolving port conflicts, optimizing network configurations, and meeting specific operational or compliance requirements.

In many cases, changes to the listen port require updates to the base URL. For example, when proxy or port forwarding is not employed and end users access the service directly through its designated listen port. In this situation, the listen-port and base-url should be changed together.

If a proxy or port forwarding is employed, the port in the base URL may not correspond to the listen port because clients can communicate with the proxy on a different port. In this case, modifying the listen port should be accompanied by updating the proxy or port forwarding configuration.

If the proxy URL differs from the previous base URL, the base URL should also be updated. This situation can arise when a proxy was not used before or when the proxy has been reconfigured to listen on a different host or port. In such cases, the old base URL is likely to be outdated.