Tips
Generate Keys
Section titled “Generate Keys”Reality keypair:
shoes generate-reality-keypairOptional Reality post-quantum authentication keys:
shoes generate-reality-mldsa65-keypairKeep mldsa65_seed on the server; distribute only mldsa65_verify to clients.
Shadowsocks 2022 password:
shoes generate-shadowsocks-2022-password 2022-blake3-aes-256-gcmUUID:
uuidgenTLS certificate fingerprint:
openssl x509 -in cert.pem -noout -fingerprint -sha256Security Best Practices
Section titled “Security Best Practices”- Use strong, random passwords
- Keep private keys secure
- Use
127.0.0.1instead of0.0.0.0for local-only access - Use firewall rules to restrict access
- Enable client certificate authentication for sensitive services
- Use Vision with Reality for maximum privacy
Performance Tips
Section titled “Performance Tips”- Enable
vision: truefor TLS-in-TLS scenarios - Use
tcp_settings.no_delay: truefor low latency - Set
quic_settings.num_endpointsto match worker threads - Use QUIC transport for high-latency or lossy networks
Common Issues
Section titled “Common Issues”- “Address already in use”: Change port or stop conflicting service
- “Permission denied”: Ports < 1024 require root/admin
- Reality connection fails: Verify keys match, UUID matches, SNI matches server’s reality_targets key
- Vision not working: Ensure inner protocol is VLESS
- Config validation fails: Run with
--dry-runfor detailed errors