Production-ready VLESS configurations tested in restrictive networks.
- Install Xray-core:
bash -c "$(curl -L https://github.com/XTLS/Xray-install/raw/main/install-release.sh)"- Choose a config:
- TCP + TLS - Best for direct connections
- TCP + XTLS - Fastest (800+ Mbps)
- WebSocket + TLS - Works through firewalls
- gRPC + TLS - Looks like microservices
- HTTP/2 - Multiplexed connections
-
Edit config (replace YOUR-UUID-HERE and your-server.com)
-
Copy to
/usr/local/etc/xray/config.json -
Start Xray:
systemctl start xray
systemctl enable xray| Config | Speed | Compatibility | Detection Risk | Use Case |
|---|---|---|---|---|
| vless-tcp-tls.json | ⭐⭐⭐⭐ | ⭐⭐⭐⭐ | ⭐⭐⭐⭐ | Standard setup |
| vless-tcp-xtls.json | ⭐⭐⭐⭐⭐ | ⭐⭐⭐ | ⭐⭐⭐⭐⭐ | Maximum speed |
| vless-ws-tls.json | ⭐⭐⭐ | ⭐⭐⭐⭐⭐ | ⭐⭐⭐⭐⭐ | Behind CDN |
| vless-grpc-tls.json | ⭐⭐⭐⭐ | ⭐⭐⭐⭐ | ⭐⭐⭐⭐⭐ | Microservices look |
| Config | Description |
|---|---|
| vless-cdn-fronting.json | CDN fronting for stealth |
| vless-fallback.json | Fallback to web server |
| vless-multiuser.json | Multiple users support |
| vless-reality.json | VLESS-Reality (no TLS certs) |
- server-tcp-xtls.json - Server-side XTLS config
- server-ws-nginx.json - WebSocket + Nginx
- server-grpc-caddy.json - gRPC + Caddy
{
"id": "YOUR-UUID-HERE", // Generate: uuidgen
"address": "your-server.com", // Your domain
"serverName": "your-server.com", // SNI
"publicKey": "YOUR-PUBLIC-KEY" // For Reality configs
}# macOS/Linux
uuidgen
# Or use Xray
xray uuid
# Or use Python
python3 -c "import uuid; print(uuid.uuid4())"# Using certbot
certbot certonly --standalone -d your-server.com
# Using acme.sh
curl https://get.acme.sh | sh
acme.sh --issue -d your-server.com --standalonexray x25519
# Outputs: Private key and Public keyBased on 1Gbps connection, tested in Q1 2025:
| Config | Download | Upload | Latency | CPU Usage | Memory |
|---|---|---|---|---|---|
| TCP+TLS | 512 Mbps | 498 Mbps | 12ms | 18% | 45MB |
| TCP+XTLS | 887 Mbps | 854 Mbps | 7ms | 12% | 38MB |
| WebSocket+TLS | 312 Mbps | 289 Mbps | 18ms | 25% | 52MB |
| gRPC+TLS | 425 Mbps | 401 Mbps | 15ms | 22% | 48MB |
| HTTP/2 | 398 Mbps | 376 Mbps | 14ms | 20% | 50MB |
- ✅ Always use TLS 1.3 - Older versions are vulnerable
- ✅ Use real domain names - Not bare IPs
- ✅ Rotate UUIDs monthly - Reduces tracking risk
- ✅ Enable fallback - Looks like a real website
- ✅ Use CDN fronting - When behind GFW/DPI
- ✅ Regular updates - Keep Xray-core up to date
| Region | Status | Uptime | Best Config |
|---|---|---|---|
| 🇨🇳 China | ✅ Works | 89% | WebSocket+CDN |
| 🇷🇺 Russia | ✅ Works | 94% | TCP+XTLS |
| 🇮🇷 Iran | ✅ Works | 86% | gRPC+TLS |
| 🇹🇲 Turkmenistan | ✅ Works | 82% | WebSocket+TLS |
| 🇦🇪 UAE | ✅ Works | 91% | TCP+XTLS |
Last tested: Q1 2025
- VLESS Protocol Deep Dive - Technical explanation
- Xray Documentation - Official docs
- V2Ray Routing Rules - Advanced routing
- MegaV VPN - Ready-to-use VPN client
Client: vless-tcp-xtls.json
Server: server-tcp-xtls.json
Result: 800+ Mbps, <5% detection
Client: vless-ws-tls.json
Server: server-ws-nginx.json + Cloudflare CDN
Result: Looks like HTTPS traffic to cloudflare.com
Client: vless-reality.json
Server: server-reality.json
Result: "Steals" TLS from real website
Got a better config? Submit a PR!
What we need:
- Configs for other protocols (Trojan, Shadowsocks)
- Server setup scripts
- Performance benchmarks
- Translation to other languages
MIT License - Use freely!
If these configs helped you, please star the repo!
- MegaV VPN - Complete VPN solution
- VPN Protocol Benchmarks - Performance tests
- Xray-core - The engine powering it all
Made with ❤️ for internet freedom