Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


A REALITY short ID is a small client-selected value that must match one entry in the server's configured shortIds list. It helps the REALITY server decide whether an incoming handshake carries an accepted configuration value. It is only one check in the REALITY authentication path: a matching short ID does not replace the server public key, the permitted server name, compatible software, or the later VLESS user ID.[1]
The complete VPN guide maps the wider connection path. This article stays at the short-ID field boundary so that a formatting or selection error is not confused with every other VLESS or REALITY setting.
This guide follows the official documentation listed below and has not been tested end to end on a live client/server pair. Check the schema and supported behavior for your installed versions before applying the checks.
Key Takeaways
- The client uses singular
shortId; the server publishes an acceptedshortIdslist.- The client value must equal one configured entry after applying the documented hexadecimal format.
- A short ID can contain at most 16 hexadecimal characters and must have an even number of characters.
- An empty value works only when the server accepts the normalized all-zero eight-byte value.
- Treat short IDs as sensitive configuration metadata even though they are not encryption keys.
Project X defines shortIds on the REALITY server as a list used to distinguish different clients. The client has one shortId, and that value must be one of the server entries.[1] The relationship is set membership, not negotiation: the client does not send a collection and ask the server to choose.
The word “ID” can be misleading because the field does not name a human account. It is closer to a compact selector inside the REALITY authentication configuration. Several authorized profiles can use distinct entries, allowing an operator to separate configuration groups or rotate one value without changing every profile at once. The exact operational grouping is an administrator choice, not a protocol guarantee.
Figure key: 1 is the single client shortId; 2 is membership checking against the server shortIds[] list and its documented hexadecimal format; 3 is the later REALITY authentication path. The arrows describe configuration relationships, not literal packet fields or a complete handshake timeline.
shortId match shortIds?The comparison is exact after the hexadecimal text is decoded into its effective eight-byte value. If the server lists 6ba85179e30d4fc2, a client configured with different non-zero digits, an inserted separator, or an odd number of characters does not refer to that entry. Friendly profile names and JSON comments are not substitutes for the actual parsed value.
The official configuration permits zero to sixteen hexadecimal characters, with an even number of characters. The core places the decoded bytes at the beginning of an eight-byte value and pads the remaining bytes with trailing zeroes. For example, aa1234 normalizes to the same value as aa12340000000000; adding zeroes at the front of aa1234 changes the value.
The documentation explicitly permits an empty client value when the server list contains an empty string.[1] In Xray v26.3.27, both sides decode into zero-initialized eight-byte buffers and the server matches those bytes: "", "00", and "0000000000000000" are the same all-zero selector. An empty client value therefore also matches a server entry written as all zeroes; the literal empty string is sufficient, not necessary. An empty server list [] is rejected by this version.[4][5] These equivalent spellings are not distinct rotation entries: removing one spelling leaves the selector accepted if another remains. Use the authorized effective value rather than guessing zeroes.
| Check | Client side | Server side | Meaning of failure |
|---|---|---|---|
| Field name | shortId | shortIds | Singular/plural placement may be wrong |
| Type | One string | List of strings | Import or schema error |
| Alphabet | Hexadecimal | Hexadecimal | Value cannot meet the documented format |
| Length | Even, at most 16 characters | Same per entry | Entry is malformed or copied incorrectly |
| Membership | One normalized value | Same normalized server entry | REALITY authentication cannot use that selector |
| Empty value | Empty client selection | All-zero eight-byte selector accepted | Empty is rejected when that effective value is absent |
Do not silently “repair” an odd-length value by guessing where a zero belongs. Obtain the intended value from the authorized configuration source. Only the documented trailing-zero normalization preserves a shorter value; adding leading zeroes to a non-zero value or inventing digits during troubleshooting changes the selector.
Short IDs are deployment selectors, not an account or subscription plan. If their distribution and rotation exceed the maintenance you want to take on, compare who maintains a VPS and a managed VPN before choosing another connection workflow.
If that server exists only to give your own devices an internet exit, AethoVPN removes the selector bookkeeping rather than simplifying it. A REALITY deployment needs a shortId that already appears in shortIds before each new phone or laptop can connect, and retiring one profile means editing the list without breaking the rest. With AethoVPN, a Windows, Android, or Debian/Ubuntu .deb device joins by signing in to your account with an email verification code, and the plan sets how many can connect at once: one mobile device on Standard, two desktop and two mobile devices on Pro, or eight of any type on Premium. What you track becomes a device count, not a list of hexadecimal entries.
To confirm a newly added device, pick a location in the app (a green load indicator marks a server in good condition, and the smart-recommended node is a reasonable first choice), connect, and repeat the online task that made you question the short ID. Because AethoVPN's website publishes no protocol details, that working connection is not a comparison point for your own server, whose shortIds entries still have to match the authorized configuration if you keep running it. Create an account with your email if per-device selectors are the part you want to stop maintaining.
A mismatch proves only that this short-ID check cannot succeed for that attempt. Depending on the implementation and configuration, the client may see an early disconnect or a generic handshake failure, while traffic that fails REALITY authentication may follow the configured target or fallback behavior.[1] The visible symptom is not guaranteed to say “short ID mismatch.”
It does not prove that the network blocked REALITY, that the server public key is wrong, or that the VLESS UUID was rejected. Those checks occupy different layers. A server may be reachable and still reject the short ID. Conversely, correcting the short ID may reveal a later public-key, server-name, UUID, flow, routing, or DNS problem.
Use the first differing stage as evidence. If the intended listener sees the connection and the authorized key and server-name values are already verified, comparing the short ID becomes reasonable. If the server sees no connection, changing the short ID cannot repair DNS, address, port, firewall, or routing failures.
The VLESS UUID identifies an allowed VLESS user at the proxy-protocol layer.[3] The REALITY client public-key material corresponds to the server's private key and participates in the outer authentication design. The short ID is another REALITY configuration selector. Combining all three under “password” makes rotation and diagnosis unsafe.
| Value | Layer | Primary question | Do not infer |
|---|---|---|---|
REALITY shortId | REALITY | Is this selector in shortIds? | Human identity or encryption strength |
REALITY password | REALITY client config | Does this public-key material correspond to the server key? | Website certificate ownership |
VLESS id / UUID | VLESS | Is this proxy user allowed? | Device ownership or REALITY success |
serverName | TLS-facing REALITY config | Is this name permitted and coherent with the target? | User authorization |
flow | VLESS/XTLS configuration | Which supported flow algorithm is selected? | QoS or route choice |
VLESS, REALITY, and XTLS Vision explains these layer boundaries. Keeping separate labels in an inventory is more useful than storing a single opaque “profile credential.”
Start with an owner and an inventory. Record which authorized configuration group receives each entry, when it was issued, which server list contains it, and when it should be removed. Do not publish actual values in a general runbook. A label such as “mobile-test-2026-09” belongs in the inventory; the literal short ID belongs in the protected configuration system.
For rotation, add the new server entry first, deploy and verify that exact list, update the intended clients through an authenticated channel, then remove the old entry after the agreed overlap. This order avoids an unnecessary outage. It also preserves a rollback point while clients are being updated.
Distinct values can narrow which configuration group is stale, but they are not a complete identity or revocation system.[2] If several people share a copied profile, a distinct short ID cannot prove which person made a request. Use the VLESS user inventory, access controls, and operational logs according to policy rather than assigning the short ID a role it does not have.
Minimize retention in logs. A partial fingerprint, configuration revision, and result category are normally enough for correlation. Do not place full profiles, UUIDs, private keys, or short IDs in screenshots, public tickets, shell history, or analytics events.
Freeze one attempt: timestamp with time zone, client and server versions, configuration revision, endpoint, and exact error category. Confirm that the client reached the intended listener. Then compare authorized representations of the parsed client shortId and server shortIds, not two screenshots that may hide or normalize the field.
Check the field name and location, the string type, hexadecimal characters, even length, and exact membership. Confirm whether the all-zero selector is intentional, including equivalent spellings. If a management system generated the value, inspect its exported configuration rather than assuming the UI label equals the transmitted setting.
Next verify the neighboring REALITY fields independently: the current client password public-key material, the selected serverName, target-related configuration, clock, fingerprint option, and version compatibility. Why the REALITY target matters covers the target contract; the layered failure checklist shows when to move to VLESS and routing.
Change one variable per hypothesis. If adding the exact authorized short ID moves the failure to a later stage, record that transition and finish the later diagnosis. If nothing changes, restore the baseline rather than cycling through random values. Repeated guessing can trigger controls, lose the original evidence, and distribute more sensitive configuration.
shortId must normalize to the same eight-byte value as one server shortIds entry.It is not a private encryption key, but it is sensitive configuration metadata used in authentication. Avoid publishing it or placing it in logs and screenshots.
The configuration can allow that, but the value then cannot distinguish those clients by itself. Use an intentional inventory and separate VLESS users when accountability or revocation requires it.
No. The documented maximum is sixteen hexadecimal characters and the length must be even. The core pads shorter decoded values with trailing zeroes to eight bytes.
No. The server must accept the normalized all-zero eight-byte value, and the other checks must pass. In Xray v26.3.27, an entry written as "", "00", or "0000000000000000" accepts that same value.[4][5]
Not necessarily. It may appear as a generic handshake rejection or early disconnect, so correlate both authorized endpoints and verify one field at a time.
No. The short ID belongs to REALITY configuration matching; the UUID identifies an allowed user in the VLESS layer.
Only when evidence points to the REALITY authentication stage. A site failure after an authenticated session is more likely to involve local capture, DNS, routing, server forwarding, or the destination.
Disclaimer: This article is general technical information for authorized configuration and troubleshooting. Do not guess credentials, expose profiles, or bypass a network owner's policy.
Sources:
Sources checked 9 October 2026.
Related Articles:
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.