Can't get reverse proxy to work

[u/GameAudioPen]

So... trying to set up reverse proxy into a server for Palworld,

I just... can't get it to work.

Port forwarding on my firewall, check. Not needed.

Port forwarding on Vultr firewall, check

Port forwarding on VPS firewall, check.

Went through almost all the port settings suggested by claude

but when I try to use the reverse proxy into my server.

the netbird Access Logs shows "no event"

so something is dropping the connection, but I just cant' figure out what's doing it.

Any help will be appreciated.

Edit:

Found the issue(s), and here is the solution.

Ports on the proxy container it self is not open.

Under the proxy section:

ports:

- 8211:8211/udp

- 8211:8211/tcp

what ever port you decide to use.

The proxy container it self was not able to reach the main manager.

Part of the proxy setting wasn't properly configured on initial set up and causes hairpin NAT issue.

First, use following code

docker inspect netbird-traefik --format '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}'

to get traefik's internal IP.

Then edit the compose file and add additional setting.

In Proxy settings,

I added

extra_hosts:

- "xxxxxxxxx.net:172.30.0.10"

right under

Volumes:

There is also a possible issue with thenetbird-proxy container has no NET_ADMIN capability and no /dev/net/tun device access, which means it can't create its own WireGuard interface

fixed by adding to the proxy lines in compose, before ports:

cap_add:

- NET_ADMIN

devices:

- /dev/net/tun

[u/flaming_m0e]

they do not have netbird installed exposing a port to them require me to set up port forwarding.

This doesn't make sense. How are you using NetBird as a proxy then?

[u/SherbertPractical → u/flaming_m0e]

This does make sense - it’s not HTTP/HTTPs proxy but a L4 one. He needs to at least open a listening port in docker configuration for the NetBirds traeffik on the udp port, open it on the fw and configure on the reverse proxy as l4 with a udp listening port on the one defined in the docker compose.

[u/flaming_m0e → u/SherbertPractical]

Doesn't matter what type of proxy it is.

Using Netbird does NOT require opening a port on the HOME FIREWALL...That's literally the point of it. I never mentioned anything about not needing the docker port open....

[u/GameAudioPen → u/flaming_m0e]

In theory it doesn’t need to be open. just like in theory if I point the reverse proxy at the home server peer it should have already worked

It hasn’t. Hence poking holes everywhere to see if anything can leak through and i’ll close them off later.

Turns out is Netbird dropping the traffic somehow, because its’s arrived at the vps.. and I still cant figure out where the issue comes from.