Use this procedure when PD Guard shows an unexpected administrator address or country. The address used for the access lock must reflect the proxy arrangement you actually operate.

Inspect before changing trust

1. Open PD Modules → Guard → Admin Access Lock and note Your IP and Your country privately.
2. Ask the administrator managing your network whether the request reaches WHMCS directly, through Cloudflare, or through another reverse proxy or load balancer.
3. Compare that arrangement with the address shown. Do not assume a country is available simply because the address is valid. A missing country can also occur for private or reserved addresses, unavailable location data, or an IPv6 address without a usable country source.

The tab and the lock use the same address resolver. The module does not accept a visitor’s forwarded address merely because an ordinary request includes a forwarding header.

Review trusted proxy ranges

In Settings, find Advanced: trusted proxy IP ranges. PD Guard recognises its built-in Cloudflare edge ranges automatically; the normal Cloudflare-only arrangement does not require adding your own connection address here.

For another proxy, obtain its precise addresses or valid ranges from the administrator who controls it. Add only the actual proxies that are meant to supply visitor addresses, then choose Save settings. Revisit Admin Access Lock and confirm the address before relying on access rules. Proxy trust is different from the administrator allow-list: this field identifies trusted intermediaries, not people who should be allowed to administer the site.

Do not add every visitor, a broad internet range or an unverified intermediary to this field. For your own proxy, the resolver walks the forwarded chain from the nearest end, skipping recognised trusted proxies. The result depends on the actual chain and how those proxies supply the header. Platform proxy settings alone are not a substitute for reviewing this module’s trusted-proxy field.

Separate address problems from country problems

The Cloudflare visitor-country header is used only when the direct connection is recognised as Cloudflare. For other connections, the module attempts country resolution from the resolved address. It does not trust a country header supplied through any arbitrary proxy.

If the address is correct but country is unknown, do not broaden proxy trust to force a country result. Review the actual access policy with your network administrator before relying on a country-only allowance. An unknown address is also important: the access lock lets that request through rather than risking a lock-out.

This check does not require changing DNS, disabling Cloudflare protection or deliberately causing failed sign-ins.

See the PD Guard WHMCS guide for related tasks, or explore PD Guard.