Summary:

When setting up an environment with two internal HTTP servers and an external HTTPS proxy managing secure traffic, the internal servers may struggle to resolve the URLs referencing them when clients try to connect. This scenario is common in cloud-based solutions such as AWS.

Description:

In this environment, the proxy has a certificate for HTTPS, but the PaperVision Enterprise (PVE) servers lack knowledge of the internal server URLs. When a server attempts to call itself, it tries to use the proxy URL (e.g., https://server.com), but it doesn’t recognize that it is actually https://server.com.

When the server tries to resolve the URL through DNS, it fails. The following steps redirect the request to http://127.0.0.1 (or http://::1 for IPv6).

1. On the webserver, navigate to C:\Program Files (x86)\Digitech Systems\PaperVision\PVEWeb.Mvc.
2. Open the file named web.config in Notepad.
3. Find the <appSettings> section and insert a new line below it.
4. Copy and paste the following value into the new line:
   a. <add key="useLocalAddrForUrl" value="true" />
5. Save the file and restart IIS.

When the ‘useLocalAddrForUrl’ setting is enabled (true), the request is directed to http://127.0.0.1 (or http://::1 if IPv6).