VeilBox

Configure a VLESS Reality profile in VeilBox

Reality is a security option for VLESS profiles in VeilBox. These instructions cover the verified Windows 2.2.0 profile form and URI parser. They configure a client for an existing server; they do not create a Reality server or supply working credentials.

Import first, then verify the profile

  1. Ask your provider or server administrator for the complete VLESS Reality link. Import the vless:// URI using profile-link import, or import the subscription that contains it.
  2. Open the profile editor. Check server address, port and UUID, then select the transport and Reality security type specified by the server. Do not assume that all Reality servers use the same port or transport.
  3. Copy SNI / server name and Public key exactly from your provider. Set Short ID, Fingerprint, Flow and SpiderX when specified. Preserve transport-specific values such as Path, Host / Authority or Service name when required.
  4. Save the profile, select it and connect. If validation fails, correct the named field. If connection fails after saving, compare the profile with the provider's original link and inspect the logs.

Fields that commonly cause errors

The URI importer recognizes pbk/publicKey and sid/shortId parameters. Its Reality validation requires a public key and SNI. A client public key is supplied by the server administrator; do not substitute a private key or generate an unrelated key locally.

Use the server's Flow and transport combination rather than copying values from an unrelated tutorial. VeilBox exposes multiple VLESS transports, but the server must accept the exact combination. Changing SNI, public key or Short ID arbitrarily will not repair mismatched server settings.

Download VeilBox

Windows: 2.2.0. macOS Apple Silicon: 2.1.0 beta. VeilBox does not include VPN servers.

Related guides

Sources and compatibility notes

Technical steps checked against VeilBox 2.2.0 Windows source. Labels can vary with the interface language. The separately published macOS beta does not establish Windows feature parity.

Windows 2.2.0 release and assets