WP Activity Log support for Reverse Proxies & Web Application Firewalls

WP Activity Log can be configured to automatically retrieve a WordPress user’s originating IP address even if WordPress is running behind a reverse proxy, web application firewall, or load balancers. The originating IP will then be shown in the WordPress activity log as the user’s IP.

This article explains how WP Activity Log can retrieve the originating WordPress user’s IP Address, and not that of the proxy, firewall or load balancer.

WordPress and Reverse Proxy or Firewall Setup

In setups with a reverse proxy, load balancer, or web application firewall, the WordPress server typically sits behind the proxy. Therefore, users never communicate directly with WordPress. Instead, users communicate with the reverse proxy and the proxy communications with WordPress, as illustrated in the image below.

Hence, in such a setup, WP Activity Log sees all the requests originating from the reverse proxy, which in this case is 192.168.2.15.

In this example, all events in the activity log will list 192.168.2.15 as the originating IP address. To record the originating WordPress user IP address, enable the option in the Reverse Proxy/Firewall Options as explained below.

Recording the originating IP Address in the WordPress activity log

To configure WP Activity Log to record the true originating IP address:

1. Navigate to WP Activity Log > Settings
2. Scroll down to the Is your website running behind a firewall or reverse proxy? section
3. Check the Yes radio button, then click on the Save Changes button at the end of the page.

Note: If after applying this setting WP Activity Log still shows the proxy/firewall/load balancer IP, enable the Filter internal IP address from the proxy headers setting.

Important note: Once the Reverse Proxy/Firewall setting is enabled, WP Activity Log will start recording the IP address from a different set of HTTP headers, which are used by proxy servers, load balancers, and firewalls. As such, this setting cannot be applied retroactively to past activities.

How the WordPress running behind a firewall or reverse proxy setting works

When the reverse Proxy/Firewall Options setting is set to Yes, the plugin retrieves users’ IP addresses from any of the below headers. In doing so, it reports the IP address of the user and not that of the firewall or proxy:

• HTTP_CLIENT_IP
• HTTP_X_FORWARDED_FOR
• HTTP_X_ORIGINAL_FORWARDED_FOR
• HTTP_X_FORWARDED
• HTTP_X_CLUSTER_CLIENT_IP
• HTTP_FORWARDED_FOR
• HTTP_FORWARDED
• REMOTE_ADDR
• HTTP_CF-Connecting-IP (used by Cloudflare)
• HTTP_TRUE_CLIENT_IP (used by Cloudflare)

These headers are used by proxy servers, firewalls, and load balancers to identify the originating IP address of a client. The below screenshot shows the headers of a connection being forwarded via a reverse proxy:

By default, when the setting is enabled, WP Activity Log reports the first IP address from the left as the originating one. This is in compliance with the relevant RFC standards.

Note: WP Activity Log still stores all IP addresses in the headers as explained in the section Retrieving all IP addresses reported in the HTTP Headers.

In some cases, however, the connection between a WordPress user and a WordPress website can be routed through several network hops. In such cases, the header will include multiple IP addresses. WP Activity Log can work around this, as explained in the next section.

Filter Internal IP Addresses Plugin Setting

By enabling the option Filter internal IP addresses, WP Activity Log plugin will not report the end user IP address should it be an internal IP address.

This option has been implemented because, in some cases, there is the possibility that an internal IP is reported in the HTTP headers rather than a public IP address.

Retrieving All IP Addresses Reported in HTTP Headers

When the Reverse Proxy/Firewall Option is enabled, WP Activity Log records all of the IP addresses specified in the HTTP header. However, it only displays the first one from the left since this should be the WordPress user’s originating IP address as per the RFCs.

That being said, there might be cases where some servers do not follow the RFC requirements and change the order of the IP addresses in the HTTP header. In such situations, should you wish to see all the IP addresses reported in the HTTP headers, follow the below procedure:

1. Navigate to WP Activity Log > Log viewer
2. Click on the More details… button of the activity for which you would like to see all the data
3. Look for the OtherIPs node as highlighted in the screenshot below

From the above screenshot, you can notice the HTTP_X_FORWARDED_FOR header, which tells us the originating IP. This is the same IP listed in the activity log. You can also notice the proxy’s IP address in the REMOTE_ADDR header, which in this example is 192.168.188.74.