What problem does it solve? When REALITY is blocked or the server IP must stay hidden, proxy operators need to front 3x-ui inbounds with a CDN like Cloudflare, or let several protocols share port 443 through Xray fallbacks — both of which involve subtle configuration traps that silently break clients. ## Core Features & Use Cases - CDN fronting: Create WebSocket, gRPC, or xhttp VLESS inbounds on CDN-proxied ports (443, 2053, 2083, 2087, 2096, 8443) and publish correct client links via host groups. - Port sharing with fallbacks: Configure a master TLS inbound on 443 that routes by path or ALPN to child inbounds on localhost, with PROXY protocol (xver: 2) preserving real client IPs. - Trap avoidance: Warns against xtls-rprx-vision flow on non-TCP clients, non-atomic fallback list replacement, Xray restarts dropping connections, and REALITY behind a CDN. - Use Case: Put a VLESS WebSocket inbound behind Cloudflare on port 2053, attach a host group so subscription links point at the CDN hostname, and verify with get_all_inbound_links. ## Quick Start Ask the agent to create a VLESS WebSocket inbound on port 2053 behind Cloudflare and publish it through a host group so client links use the CDN hostname.