Skip to content

docs: document 0.6.1 transport root cause #18

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Divaaaan merged 2 commits into from
Sep 16, 2026
Merged

docs: document 0.6.1 transport root cause #18

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bbeb21e
docs: document 0.6.1 transport root cause
Divaaaan Sep 16, 2026
88889a8
docs: narrow 0.6.1 transport scope
Divaaaan Sep 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 14 additions & 6 deletions docs/releases/0.6.1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,8 @@
This desktop hotfix prevents failures in Tenebra's on-connect,
multi-destination node validation from being reported as an
all-servers-unreachable result. It also makes failures in the server list's
separate direct TCP status checks visible.
separate direct TCP status checks visible and prevents one incompatible
subscription node from invalidating the shared sing-box configuration.

- The on-connect validation reserves a free contiguous block of loopback ports
instead of relying on a fixed range that another local process may already
Expand All @@ -18,6 +19,11 @@ separate direct TCP status checks visible.
all-servers-unreachable verdict.
- Probe stdout and stderr are retained in a bounded tail for diagnosis and are
scrubbed before being logged or returned through the control interface.
- Imported VLESS URLs with unsupported stream transports, including `xhttp`,
are excluded before the shared probe or tunnel configuration is built.
VLESS nodes using QUIC without its required TLS are excluded for the same
reason, while compatible VLESS QUIC nodes remain supported. Other usable
nodes in the profile stay available.
- Separately, the server list shows whether its direct TCP status checks are in
progress, ready or failed and provides a retry action. An earlier successful
RTT may remain visible while a refresh runs or fails, but it is marked stale
Expand All @@ -27,8 +33,10 @@ separate direct TCP status checks visible.

Automated tests cover the on-connect validation's probe ownership, lifecycle
and port races, authenticated readiness, bounded log capture and the bundled
sing-box configuration, plus the server list's direct TCP states. The precise
trigger of the original unavailable-server report on the affected machine has
not been causally reproduced. Native installation, service, ordinary-user UI
and tunnel checks of the exact signed candidate remain required before
publication.
sing-box configuration, builder-level unsupported-transport isolation and
compatible VLESS QUIC, plus the server list's direct TCP states. The affected
profile reproduced the original failure in a retained Windows VM: one `xhttp`
entry made the bundled sing-box reject the shared configuration with `unknown
transport type: xhttp`, blocking otherwise usable nodes. Native installation,
service, ordinary-user UI and tunnel checks of the exact rebuilt signed
candidate remain required before publication.
Loading