---
title: "Discussion on \"Why SafeLine WAF Isn’t Showing the Right IP — and How to Fix It\" | Hashnode"
description: "Discussion on \"Why SafeLine WAF Isn’t Showing the Right IP — and How to Fix It\". When deploying SafeLine WAF behind CDNs or reverse proxies, it’s common to run into source IP address issues. If your logs show internal or incorrect IPs instead of real client IPs, this guide will help you identify and fix the problem step by step.\n..."
url: "https://hashnode.com/posts/why-safeline-waf-isnt-showing-the-right-ip-and-how-to-fix-it/683959b8aa69e1517a8f2b0e"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why SafeLine WAF Isn’t Showing the Right IP — and How to Fix It](https://your-firewall-is-lying-to-you.hashnode.dev/why-safeline-waf-isnt-showing-the-right-ip-and-how-to-fix-it?utm_source=hashnode&utm_medium=feed)

When deploying SafeLine WAF behind CDNs or reverse proxies, it’s common to run into source IP address issues. If your logs show internal or incorrect IPs instead of real client IPs, this guide will help you identify and fix the problem step by step. ...

May 30, 2025 · 3 min read · your-firewall-is-lying-to-you.hashnode.dev  
Read the article

-   [#safeline](https://hashnode.com/tag/safeline)
-   [#waf](https://hashnode.com/tag/waf)
-   [#web-development](https://hashnode.com/tag/web-development)
-   [#developers](https://hashnode.com/tag/developers)

## Written by

[Sharon](https://hashnode.com/@sharon772)

@sharon772

  
[View profile](https://hashnode.com/@sharon772)

## Responses 1

Markdown supported · ⌘↵ to post

[CDN Edge Ops](https://hashnode.com/@cdnedgeops)

[Nov 9](https://hashnode.com/posts/why-safeline-waf-isnt-showing-the-right-ip-and-how-to-fix-it/683959b8aa69e1517a8f2b0e/comment/6af23ee0b9e17432e02e10c6)

When a WAF sits behind another reverse proxy or edge, the source address it logs is often the hop that connected to it, not the client. Trust only an explicit forwarded-client header after you strip or overwrite it at the trusted perimeter; if every hop appends without a trusted rewrite, spoofed client addresses sail into rate limits, allow-lists, and audit trails. Prefer a single rewrite at the outermost trusted proxy that sets the real client once, then ignore further inbound copies of that header from the open internet.

Ops prove-out after the rewrite: send a probe with a forged forwarded-client header and confirm the WAF decision and access log both show the address of the trusted hop (or the rewritten value you control), not the forged one. Compare allow-list and rate-limit counters before and after with the same client path — if blocks suddenly target your load balancer instead of abusers, the trust boundary is still reading the wrong hop. Keep health-check and internal probe paths on a separate allow path so they do not inflate the shared client-IP budget.
