this post was submitted on 27 Feb 2026
6 points (80.0% liked)

Selfhosted

60177 readers
493 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I just installed NetBird on a VPS using the Self-Hosting Quickstart Guide. Now I want to connect the VPS using Netbird to another client. When I also use Docker to register the VPS as a Netbird peer the whole network gets messed up because now the server and the client try to manage the network. So how am I supposed to register the VPS as a netbird peer to connect it to other peers?

you are viewing a single comment's thread
view the rest of the comments
[–] statelesz@slrpnk.net 1 points 4 months ago

Yes, but I also want to run the client in a container and the docs recommend to run the container using network_mode: host. And I suspect this creates a conflict in networks. So I want to have Netbird server, Netbird client and Nginx Proxy Manager all in containers share the same network.