Anyone have any trouble getting the p2p going?

[dfreshindahouse]

Just curious to see if anyone has had any trouble.

[A561988]

Was working for me earlier today.

[dred238408-cloud]

I didn't run into any problems at all; everything worked as it should.

[VGIL77]

Connectivity should be much better now. A few updates since this thread:

• Public bootnode is live at p2p.bitterbot.ai (resolved via DNS TXT → multiaddrs). The orchestrator picks it up automatically via the bootstrapDns config.
• Circuit relay (auto) — if your node isnt directly reachable (NAT/firewall/double-NAT), the orchestrator uses the bootnode as a relay so you can still participate in the mesh.
• dcutr hole-punching — after relaying connects you to a peer, it attempts a direct connection upgrade. Works for most residential setups.
• DNS bootstrap with retry + timeout — 10s timeout per lookup, up to 2 retries, graceful fallback to configured static peers if DNS is blocked.

If P2P still isnt going for you, run:

bitterbot doctor

The P2P Network section probes:

• Orchestrator binary availability
• DNS bootstrap resolution for p2p.bitterbot.ai
• TCP reachability to the fallback bootstrap peer
• Live peer count from the running orchestrator

If that surfaces anything red, drop the output here and well dig in. Most failures come down to egress firewalls blocking TCP 9100, or the orchestrator binary not being built (cargo build --release --manifest-path orchestrator/Cargo.toml).

[VGIL77]

Quick update, we've tightened this up further since my last reply.

Public bootnode is live and deployable. The deploy/bootnode/ dir now has a full Dockerfile, Railway config, and README covering DNS TXT setup (_dnsaddr.p2p.bitterbot.ai), peer ID persistence via mounted volume, and Circuit Relay v2 server mode. Idle footprint is ~20-30 MB, so anyone who wants to run their own bootnode can do it on a cheap VPS.

Wizard now has a dedicated P2P onboarding step (src/wizard/onboarding.p2p.ts). On first run it:

1. Probes for the orchestrator binary across the 4 resolution paths (config override, cargo release/debug, ~/.bitterbot/bin) and tells you which it found.
2. Resolves _dnsaddr.p2p.bitterbot.ai with a 5s timeout and reports live peer count.
3. TCP-probes the fallback bootstrap peer and measures RTT, catching firewall/egress issues before runtime.
4. Auto-writes desktop/.env with the gateway URL and token so the Vite Control UI connects on first pnpm dev (no more copy-paste).

Opt-out is available in advanced mode but quickstart keeps P2P on by default.

bitterbot doctor still works as the diagnostic for anyone already past the wizard. If P2P still doesn't come up, drop the doctor output here and we'll dig in.

[OhhJJ]

Yeah, we ran into a couple of hiccups getting P2P up initially, mostly around config and connectivity, but nothing too serious. Sorted it out pretty quickly once we double-checked the setup and logs. Working stable now 👍

[sinstaik]

Everything's fine!