NetBird proxy worked only with each exact subdomain
A local Debian server runs Docker, with Caddy handling the and certificates and AdGuard Home resolving local . Services such as Nextcloud already work on the and through Tailscale.
A NetBird was installed on that same server, and AdGuard Home was configured as the name server. NetBird returned a 502 error when the target was the , a , the server's private IP address, or the entire range.
The connection worked when the target resource was the exact subdomain, such as nextcloud.example.com. This means each service, including Paperless, currently needs its own subdomain resource; the available details do not establish whether that is expected NetBird behavior or a problem.
Key points
- NetBird worked when the target was an exact service subdomain.
- A produced a 502 error.
- The server's private IP address and the full range also failed.
- Each can be added as a separate NetBird resource as a workaround.
- The existing Caddy setup continued to work locally and through Tailscale.