docs: reconcile socat bridge claims (verified on VM), fix Unraid template - #19
Merged
Conversation
…mplate - Verified on VM (v1.0.1 image): socat bridge works end-to-end via bridge networking + published port (full WS 101 handshake). Critical caveat: SIMPLEX_SOCAT_PORT must differ from 5225 — the daemon already binds 127.0.0.1:5225, so socat's bind of 5225 fails 'Address already in use'. Both README and template previously recommended 5225. - README Network Configuration now states verified behavior + auth warning; env table and multi-bot FAQ updated consistently; removed 'under investigation / not confirmed' language. - Template Overview corrected to match; SIMPLEX_SOCAT_PORT description updated with must-differ-from-5225 + unauthenticated warning. - Port 5225 field annotated as informational-only under host networking. - Added dated Changes entry.
libre-7
added a commit
that referenced
this pull request
Aug 24, 2026
docs: reconcile socat bridge claims (verified on VM), fix Unraid template
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
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
Resolves the socat documentation contradiction flagged in the 2026-08-23 review.
Verified behavior (tested live on a VM against the v1.0.1 image, bridge networking, published host port):
HTTP/1.1 101 Switching Protocols) through the published port.SIMPLEX_SOCAT_PORT=5225— as both README and the Unraid template previously instructed — ALWAYS fails withsocat[...] E bind(5, {AF=2 0.0.0.0:5225}, 16): Address already in use, because the daemon itself already binds 127.0.0.1:5225. The port must be anything else (e.g. 5226).Changes