Skip to content

Pairing off the tailnet: name a reachable address, not 0.0.0.0 - #54

Merged
i2cjak merged 1 commit into
mainfrom
backplane/pair-self-url
Oct 6, 2026
Merged

i2cjak merged 1 commit into
mainfrom
backplane/pair-self-url

Conversation

@i2cjak

@i2cjak i2cjak commented Oct 6, 2026

Copy link
Copy Markdown
Collaborator

Found in a real desktop <-> h@backplane test of v0.11.0. A hub started with --no-tailscale --host 0.0.0.0 told its BACKPLANE_PEERS machines its address was http://0.0.0.0:PORT when pairing, so the other side refused it (403: not one of the machines this hub found). Pairing now gives the address the hub's machine list found for it (self.url); every address a hub reports also honours BACKPLANE_URL. With the fix, the two machines paired and passed the whole real test: create a project on backplane from the desktop, live text, a reply from a real Claude, and a desktop agent's thread_send/thread_wait to backplane's thread. Hubs on the tailnet already paired through Tailscale identity and are unaffected.

…und for it (or BACKPLANE_URL), never the 0.0.0.0 it listens on
@i2cjak
i2cjak merged commit 28d9754 into main Oct 6, 2026
4 checks passed
Snaiderbg pushed a commit to Snaiderbg/Backplane that referenced this pull request Oct 9, 2026
UI fixes, /btw, light mode, headless mode, faster phone app with a fuller viewer, KiCad checks, and release packages
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant