So what I've been reading is use tail scale it's much easier and works..

Edited March 28Mar 28 by ap90033

On 3/3/2026 at 10:05 AM, rguinn said:

I having a issue where overtime the container updates it create a new peer on my host - Any idea why this would be happening?

@jimrummy101 heads up that the container path for appdata needs to be updated.


@rguinn
change the appdata container path to "/var/lib/netbird"
currently its /etc/ or something

time to map (insert number here) services to this new client again.

Groundhog Day loop because the appdata path isn't persisting. Here is the play-by-play of the failure:

1. Handshake: "Hey server, here is my setup key. Who am I?"

2. Authentication: "Server says I'm Node-A. Awesome, here’s my access."

3. The Oversight: "I'll just tuck this identity into /etc/netbird... oh wait, that's not a persistent volume? Guess I'll just keep it in RAM. YOLO."

4. The Reboot: [System restarts]

5. The Amnesia: "I have no traces of appdata. I have no key. I am a blank slate. Hey server, here is my setup key... who am I?"

6. The Result: The dashboard now shows Node-A (Offline) and Node-B (Online). Rinse and repeat until your dashboard is a graveyard of ghost nodes.
   
   
   

Edited April 4Apr 4 by Salpertia

Ok I have installed the docker netbird client container and was not able to ping the unraid host on the 100.x.x.x address.

I had to use the following script to make this work with network type host.

#!/bin/bash
# netbird-iptables-all.sh - Allow ALL traffic on wt0 (Netbird) for Unraid

if ! ip link show wt0 >/dev/null 2>&1; then
echo "Error: wt0 not found. Start Netbird first."
exit 1
fi

# Full ACCEPT for all protocols/ports on wt0
iptables -I INPUT 1 -i wt0 -j ACCEPT && echo "INPUT -i wt0 ALL"
iptables -I OUTPUT 1 -o wt0 -j ACCEPT && echo "OUTPUT -o wt0 ALL"
iptables -I FORWARD 1 -i wt0 -j ACCEPT && echo "FORWARD -i wt0 ALL"
iptables -I FORWARD 1 -o wt0 -j ACCEPT && echo "FORWARD -o wt0 ALL"

# Extra for Docker/NAT if needed
iptables -t nat -I POSTROUTING 1 -s 100.64.0.0/10 -o br0 -j MASQUERADE

#iptables-save > /boot/config/iptables.conf
echo "All wt0 traffic allowed. Test: http://[Unraid Netbird IP] from Android"
echo "Netbird IP: $(ip addr show wt0 | grep 'inet ' | awk '{print $2}' | cut -d/ -f1)"

I've recently setup, and I had it working (I'm just using it for access to Unraid from remote devices) as an alternative to Tailscale.

However, I did a reboot and, while everything was fully functional, after a reboot of my server I can't get anywhere. Everything seems to start fine, I can still connect my remote client to it, but from that client I can't ping or open the unraid server.

Any suggestions on how to troubleshoot that?