Fix: Auto-remove multiplex when VLESS uses xtls-rprx-vision flow #907
Conversation
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
Implements intelligent conflict detection between multiplex and xtls-rprx-vision flow. When generating inbound configuration, automatically removes multiplex if any user has Vision flow configured, as these two features are incompatible. Technical background: - Multiplex adds protocol layer headers for connection multiplexing - Vision flow requires direct TLS access to analyze traffic patterns - Mux headers prevent Vision from inspecting TLS handshakes - This causes 'REALITY: processed invalid connection' errors Solution: - Added conflict detection in addUsers() and initUsers() functions - Dynamically removes multiplex from configuration when Vision flow detected - Preserves multiplex for users without Vision flow - No database modification required - works at runtime Related issues: alireza0#224, alireza0#228, alireza0#474, alireza0#528
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Problem
When VLESS inbound has both
multiplexand users withflow=xtls-rprx-vision, connections fail withREALITY: processed invalid connectionerrors. These two features are mutually exclusive:Solution
This PR implements intelligent conflict detection at runtime:
Backend Changes (
service/inbounds.go)addUsers()andinitUsers()functionsxtls-rprx-visionflow configuredFrontend Changes (
frontend/src/types/inbounds.ts)multiplex: {}from VLESS default templateBenefits
✅ Automatic conflict resolution at runtime
✅ No manual intervention required
✅ Preserves multiplex for non-Vision users
✅ Works with existing configurations
✅ No breaking changes
Testing
Tested on production server with 9 VLESS+REALITY clients using Vision flow:
Related Issues
Fixes #224, #228, #474, #528
Impact
This fix will benefit all s-ui users who use VLESS+REALITY+Vision configuration, which is the recommended setup for anti-censorship in restrictive environments.