[Self Hosted] Reverse Proxy not reporting real IP

Riano_De_Souza · May 15, 2026, 9:43am

Describe the problem

Howsit.

I installed netbird pre 0.65 combined container setup. Did the migration activated the proxy and busy testing the reverse proxy feature. Looks very promising. Netbird itself works amazingly well, so we have no complaints there. The only issue i am having is. I am trying to setup country blocking or any IP filtering on the reverse proxy but it keeps reporting the netbird proxy docker IP instead of the external IP of the incoming connection.

So it blocks the connection because its country restricted. How do i get it to pick up the correct IP address. I am using the integrated traefik and combined docker setup.

To Reproduce

Steps to reproduce the behavior:

Configure the reverse proxy.
Access an exposed service.
Proxy Events shows internal 172.30.0.10 IP. Seems to be the docker network.

Expected behavior

External IP address to be reported and country blocking/IP Filtering then work.

Are you using NetBird Cloud?

Self Hosted

NetBird version

Latest as of today.

Management: v0.71.0

Dashboard : v2.38.0

Is any other VPN software installed?

None

Debug output

No Debug. VPN works Only reporting back the incorrect IP Address.

Screenshots

Have you tried these troubleshooting steps?

Reviewed client troubleshooting (if applicable)
Checked for newer NetBird versions
Searched for similar issues on GitHub (including closed ones)
Restarted the NetBird client
Disabled other VPN software
Checked firewall settings

*EDIT*
I solved this by following a guide provided by a user in the SLACK channel. The link below should take you there and fixed my issue.

github.com/netbirdio/netbird

Crowdsec bouncer not blocking on self-hosted combined container setup

opened 08:44AM - 04 May 26 UTC

pernetz

triage-needed

**Describe the problem** The crowdsec integration into an existing combined ser…ver is not working as expected, following the official guide [Enable CrowdSec IP reputation](https://docs.netbird.io/selfhosted/migration/enable-reverse-proxy#step-7-optional-enable-crowd-sec-ip-reputation) **To Reproduce** Steps to reproduce the behavior: 1. Running my self-hosted netbird instance on public VPS 2. Edit of `docker-compose.yml`, start crowdsec, register bouncer, configure proxy and enable service works fine (installation steps 7a to 7d). 3. Setting CS IP reputation to Enforce on proxied domain 4. Added my public IP to decisions list `sudo docker compose exec crowdsec cscli decisions add --ip 1.2.3.4 --duration 1h --reason "manual test"` 5. Proxied domain still accessable, also with incognito browser mode 6. Rolled back the entire server and retried installation 7. Still no blocking **Expected behavior** Access to the proxied domain should have been blocked after setting the access control rule. **Are you using NetBird Cloud?** Self-host NetBird's control plane on public VPS (Hetzner) **NetBird version** `v0.70.4` **Is any other VPN software installed?** None **Have you tried these troubleshooting steps?** - [x] Checked for newer NetBird versions - [x] Searched for similar issues on GitHub (including closed ones) - [x] Restarted the NetBird server

Xeravax · May 23, 2026, 6:43am

I had a similair issue, trafeak isn’t properly sending the IP address to Netbird. Still trying to figure out on my end why this is happening and I think it has to do with the headers/any real-ip plugins.

antybubbs · May 25, 2026, 8:50am

I have the same issue with me on my end. I am hosting Authentik proxied through Netbird but at some point in the Auth flow it uses the Docker internal gateway and because i have geoblock enabled it blocks the route and breaks the auth flow

Riano_De_Souza · May 25, 2026, 10:12am

@antybubbs and @Xeravax I edited the post with the solution that worked for me.

antybubbs · May 25, 2026, 6:06pm

Thanks! But this feels like a bug? Not sure if @NetBird can have this fixed?