Documentation:HardServerUrl

MDriven Server (and TurnkeyServer) adapts by looking at the incoming requests to discern what its own address is.

In certain situations this is not desired.

One example is if you have the application behind a load balancer or reverse proxy and the load balancer pings your app with an address that is not the desired server address.

This could lead to your app getting confused to what its true url should be.

To mitigate this you can create a App_Data/HardServerUrl.xml file with content like this:

<root HardServerUrl="https://theaddressyouwantyourapplicationtohave"></root>

When setting the hardserverurl in systems that also use Turnkey you should(possibly) also make sure turnkey use the proper url to mdriven server by setting the MDrivenServerOverride.xml settings.

SignalR issue: Setting HardServerUrl for the TurnkeyApplication effects the SignalRConnection so it may be required to make your Application find itself under the local server address rather than some reverseproxy address used in calling it.

This functionality is available in builds from 2019-04-17

You can verify that the HardServerUrl is in effect by checking log after start up in MDrivenServer versions after 2022-04-28:

2022-04-28 11:41:30,773 [9] INFO - <path>\App_Data\HardServerUrl.xml NOT found - App url is unchanged: https://localhost:44368

or

2022-04-28 11:41:30,773 [9] INFO - <path>\App_Data\HardServerUrl.xml found and applied:  https://localhost:44368