- Client IP Debug Panel

|

This debug panel is listing all relevant informations to debug when the detected client ip is wrong (in case of reverse proxies etc.)
Sometimes, there are proxies between your user and the wordpress server application (e.g. a CDN, reverse proxies).
This needs to be known to the plugin to choose the correct IP adress.

Current IP informations (as detected by the plugin)

Detected client IP:
This IP is used for detecting the geo-information of the user. It should be the same as the real client IP below. Real client IP (detected without the plugin): Detecting ... This IP is detected within the browser, so reverse proxies of the server are not affected.
External Server IP:
In some cases, the server is in the same network as the client (e.g. testing server). As the connection does not use Internet, this plugin uses the IP adress of the server as seen from the internet.
For performance reasons, this IP is cached for .
Also, for servers without internet access, this IP can be set in the options.

REMOTE_ADDR:
In server configurations without reverse proxy, this will equal to the "detected client IP". Otherwise, this is the IP of the reverse proxy. HTTP_X_FORWARDED_FOR:
Reverse proxies usually add this header to indicate the original IP. If several IPs are given here (seperated by a comma), the correct user IP usually is the leftmost one. (Probably you should enable the reverse proxy option.)

Settings of the plugin

• Use reverse proxy: Enable this option if REMOTE_ADDR is not the correct client IP.
• Whitelist for known reverse proxies (optional if only one): All IPs in HTTP_X_FORWARDED_FOR that are not the correct client IP are probably known reverse proxies.
  (For security reasons, this is not assumed by default: maybe the reverse proxy is not of the server, but a Man-In-The-Middle-Attack ... not very probable but possible.)