Assign Alice its own ports, next sequential#2500
Open
stupleb wants to merge 1 commit into
Open
Conversation
stupleb
force-pushed
the
fix/alice-coordinator-routing
branch
from
b0534b4 to
4c1b8e1
Compare
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.
What does this PR do?
In v0.8.5-alpha Alice and Freedomsats are wired to the same local socat ports, and Alice's nginx upstream points at Bazaar's bridge.
robosats-client.sh launches multiple socats but two collide and don't end up listening. Whichever of mainnet_alice_socat / mainnet_freedomsats_socat loses the bind() race exits with EADDRINUSE
The order-book screen on the web client never finishes loading because requests to /mainnet/alice/api/... are proxied to 127.0.0.1:107 which is Bazaar's bridge and surface Bazaar's responses (or 502s) as Alice's.