Setting up proxy ip's – Proxibolt

Overview

The Proxy IPs setting in Droppy is used when your Droppy installation is running behind a reverse proxy (such as Nginx, Apache, HAProxy, or a load balancer). In these setups, Droppy may receive the proxy’s IP address instead of the actual client’s IP address.

This setting allows Droppy to correctly determine the real IP address of users accessing the application.

Built-in Cloudflare support

Droppy has built-in support for Cloudflare.
If your Droppy site is behind Cloudflare only, you do not need to configure the Proxy IPs field.

Leave the Proxy IPs field empty when using Cloudflare.

Droppy will automatically detect and use the correct client IP provided by Cloudflare headers.

Why this setting matters

When Droppy is not behind a proxy, it can directly read the client’s IP address and no configuration is required.

When a reverse proxy is involved (other than Cloudflare):

Incoming requests appear to come from the proxy
Droppy may log or display the proxy IP instead of the real client IP
Security, logging, and auditing features may become inaccurate

Adding trusted proxy IPs ensures Droppy can correctly extract the real client IP from forwarded headers.

How Droppy detects your IP

In the Proxy IPs field description, Droppy shows the IP address it is currently detecting, for example:

Droppy is currently detecting your IP as: 192.168.1.2

If this IP matches your real client IP, everything is working correctly and the field can be left empty.
If this IP does not match your real client IP, it is likely the IP address of your reverse proxy (not Cloudflare).

In that case, add the proxy’s IP address to the Proxy IPs field.

Configuring Proxy IPs (non-Cloudflare proxies)

Single proxy

For a single reverse proxy, enter its IP address:

192.168.1.2

This tells Droppy to trust that proxy and retrieve the real client IP from forwarded headers such as X-Forwarded-For.

Multiple proxies

If multiple proxy hosts are used, separate their IP addresses with commas:

192.168.1.2, 192.168.1.3, 10.0.0.5

CIDR notation support

CIDR ranges are supported for convenience:

192.168.1.0/24

You may also combine individual IPs and CIDR ranges:

192.168.1.2, 10.0.0.0/16

When to leave this field empty

Leave the Proxy IPs field empty if:

Droppy is not behind a reverse proxy
Droppy is behind Cloudflare
The detected IP matches the real client IP
Everything is functioning correctly

Security considerations

Only add trusted proxy IPs that you control
Never add public or unknown IP ranges
Incorrect configuration may allow IP spoofing via forwarded headers