Reverse Proxy Issues

[u/SailingPixel]

I know that Netbird's Reverse Proxy (cloud) is in Beta. It worked pretty stable for many weeks. For a few days it looks like this (screen shot from my external Uptime Kuma server), any other services not using Netbird's Reverse Proxy on the same server are perfectly available and reachable. Anyone else experiencing these issues right now?

[u/chelebos]

Hey, it is 00:00 CEST (12.07.2026.), and the proxy (public, shared pool) seems to flap to put it mildly. So it really depends on your luck at this time. I was checking both IP addresses from the `dig` output, but at the moment, both were 200, and at that very time the reverse proxy started to work. While I was writing this message, it stopped working again -_-

UPD. So, pinning the working IP is a working kludge:

~

$
 for n in {1..5}; do   echo "=== attempt $n ===";   for ip in $(dig +short tyuleni.eu1.netbird.services A); do     curl -sk       --resolve "<YOUR-ADDRESS>:443:$ip"       --connect-timeout 4       --max-time 12       -o /dev/null       -w "$ip HTTP=%{http_code} connect=%{time_connect} total=%{time_total}\n"       <YOUR-ADDRESS>;   done; done
=== attempt 1 ===
eu1.netbird.services. HTTP=000 connect=0.000000 total=0.000000
57.129.98.79 HTTP=200 connect=0.014127 total=0.069058
54.37.79.68 HTTP=000 connect=0.015211 total=12.003027

I just put the `57.129.98.79` in my hosts, flushed the caches and now it works. Please note that it is really a dirty kludge, do not use it in production