fix(compose): wire buzz-pair-relay so mobile QR pairing works - #3875
Open
Chessing234 wants to merge 7 commits into
Open
fix(compose): wire buzz-pair-relay so mobile QR pairing works#3875Chessing234 wants to merge 7 commits into
Chessing234 wants to merge 7 commits into
Conversation
Membership-enforcing relays need a pairing sidecar; without it mobile/desktop QR pairing 404s on the legacy /pair path. Signed-off-by: Taksh <takshkothari09@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Point clients at the sidecar URL instead of inferring a broken /pair path from NIP-43 membership advertisement alone. Signed-off-by: Taksh <takshkothari09@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
TLS installs terminate on Caddy; route pairing traffic to the sidecar before the catch-all reverse_proxy to the main relay. Signed-off-by: Taksh <takshkothari09@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Give operators a copy-pasteable NIP-11 pairing URL for both Caddy and direct-port deployments. Signed-off-by: Taksh <takshkothari09@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Call out the TLS vs non-TLS URL shapes so self-hosters do not ship a membership relay that advertises a dead pairing path. Signed-off-by: Taksh <takshkothari09@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Avoid racing /pair traffic against a sidecar that is still binding its listen port on first boot. Signed-off-by: Taksh <takshkothari09@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Operators reading ./run.sh help should see how TLS vs direct-port pairing URLs differ before they open .env.example. Signed-off-by: Taksh <takshkothari09@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
2 tasks
Contributor
Author
|
@tlongwell-block @wesbillman @wpfleger96 mind taking a look when you get a chance? |
3 tasks
This was referenced Aug 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
buzz-pair-relaysidecar indeploy/compose(usingentrypoint, notcommand, so Compose does not append args tobuzz-relay).BUZZ_PAIRING_RELAY_URLin NIP-11 and proxy/pair*through Caddy so membership-enforcing self-hosts stop 404ing on legacy/pair..env.example, README, andrun.sh help.Fixes #3842
Test plan
cd deploy/compose && cp .env.example .env(fill CHANGE_ME) and./run.sh configsucceeds withBUZZ_PAIRING_RELAY_URLsetBUZZ_COMPOSE_TLS=true ./run.sh startbrings uppairing-relayhealthy; Caddy/pairreaches itHTTP 404BUZZ_PAIRING_RELAY_URLpoints at the published:5000portMade with Cursor