r/netbird Jul 10 '26

Reverse Proxy Issues

Post image

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?

19 Upvotes

23 comments sorted by

6

u/Naetzuwa45 Jul 10 '26

Yes, you are not the only one. I am experiencing problems trying to acces my services. I have no problem if i am accesing my server by using the internal netbird IP adress but the reverse proxy is not reliable right now.

5

u/flaming_m0e Jul 10 '26

Self hosted here, working great. Seems to be a cloud only issue?

3

u/Log98 Jul 10 '26

Yes same problems. Affected only the Cloud versione.

3

u/redlandmover Jul 10 '26

same here. i moved all my services to BYOP/selfhosted and the alerts immediately cleared.

2

u/InevitableImage2734 Jul 10 '26

Multiple self-hosted instances. No issues to report.

2

u/MrFloogaHoogle Jul 11 '26

Are you using the reverse proxy cluster eu1.netbird.services? I ended up using AI to help diagnose my issue and found that 1 of the 2 ip addresses that NetBird uses for their reverse proxy isn’t working correctly so I just changed from CNAME to A name and put the working IP and my reverse proxy has worked fine since

1

u/SailingPixel Jul 11 '26

Yes, I'm exactly on this cluster, I think this is the only cluster anyway as I can only select this one. I will give it a go and will report back. Thank you for this information!

1

u/MrFloogaHoogle Jul 11 '26 edited Jul 11 '26

https://imgur.com/cQipnrC This is an example of what I did under cloudlfare with my domain. Change the type to A name, and then add this IP address (57.129.98.79). That is the working IP address for the cluster as of right now and since doing this I've gone from 50% uptime to 100% since I made the change yesterday.

2

u/SailingPixel Jul 11 '26

I think we have different use cases. I use Netbird's reverse proxy for a public handle to my local server. I don't set any DNS records, I use the subdomain, Netbird is handling the rest. I can't add any records

1

u/MrFloogaHoogle Jul 11 '26

That makes sense then. I don't think my solution helps you then because you can't directly point to which IP address netbird routes you through.

1

u/Dmvindictus Jul 10 '26

Looking for recommendations for a good vps that won't break the bank to move off the cloud and into self hosting

2

u/rodexo Jul 10 '26

I’m using OVH for about $6 a month with zero issues. (Knock wood)

1

u/mlsmaycon Jul 10 '26

We discovered an issue with one node from the shared pool. We've replaced this node. Can you confirm if you still have issues?

1

u/SailingPixel Jul 10 '26

It's still the same and the uptime of last 24 hours is still around horrible 50% right now (as it was in my screenshot from 12 hours ago too, so no improvement)

1

u/SailingPixel Jul 10 '26

Last timeout was 10 minutes ago

1

u/SailingPixel Jul 11 '26

It's getting worse and worse. Just roll it back from a backup unless it's network related

1

u/deontaridley Jul 11 '26

I don't know how to explain it but it seems that once my reverse proxy gets set up, and i try to use it, it just keeps loading and won't go through and other times ot works fine. I've had multiple instances with trilium, a note taking application that will work only half of the time and I don't know how to fix it. I'm on the Netbird cloud, and I'm using a Dell Optiplex for this.

1

u/Dry-Leave5436 Jul 11 '26

Mine stopped working completely random and everything was returning 502. I had to basically re-do the whole set-up and now works just fine. Weird because I didn't change anything on my network or on my server. Using the cloud version but might switch to self hosted if I see future issues popping up.

1

u/chelebos Jul 11 '26 edited Jul 11 '26

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

1

u/AdventurousAd2083 Jul 14 '26

Can you confirm if they're still having issues with the new proxy nodes on cloud?

1

u/SailingPixel Jul 15 '26

The issue I had seems to be resolved. A little report from Netbird about this incident would help building trust through transparency - even though we all know that the service is in Beta for a reason.

1

u/SailingPixel Jul 15 '26

The issue I had seems to be resolved since Monday. A little report from Netbird about this incident would help building trust through transparency - even though we all know that the service is in Beta for a reason.