Overview

You have placed an Nginx reverse proxy in front of ListManager (for example, for redirect handling or network routing; see the Enforcing TLS 1.2 or 1.3 using Nginx Reverse Proxy article) and you notice that LM Clicktracking data is being recorded with your internal IPs. You have other external processes that look at those IPs and this is causing issues. You want to know if this is the result of the proxy server and whether it can be fixed.

Information

Important for ListManager 12.4.11 and later: NGINX is no longer required solely to harden HTTPS transport security. This article applies only if you still choose to deploy ListManager behind a proxy server.

This is a known limitation of this reverse proxy server setup. Nginx can forward the original IP with some headers, but LM is not coded to handle these headers and will not work if they are added. Unfortunately, there is no workaround in this case.

Related Articles

• Enforcing TLS 1.2 or 1.3 in Lyris LM Through an Nginx Reverse Proxy