Skip to content
Connect

Connect

Choose a connection plan

Set the automatic connection scope on Connect. The source dropdown in Servers only filters the list; scope shortcuts are no longer shown in the node list or manual-group management.

Open the server row on Connect. The picker separates Automatic scope, Fixed node and Complete configurations. Browsing a tab or searching does not change the saved selection; choose a resource to apply it. The plan shows the selected scope and candidate count. Custom manual groups organize browsing, not automatic connection pools.

For ordinary nodes, choose Automatic, a subscription, all manual nodes or a fixed node. Smart/Custom can use 1–3 entry servers; a fixed node or All via VPN uses one. Manage Smart, All via VPN and custom profiles from Routing. Smart/ordinary Custom expose DNS, sniffing and proxy selection; system tunnel exclusions still determine which traffic enters Xray.

Automatic selection without a test prerequisite

Active, readable ordinary candidates with successful cached latency rank by duration and ID. Untested, failed and timed-out results follow by ID. Connecting does not start, await or retry latency tests, and missing results do not block startup. The final-exit node is excluded from entry selection; a selected final exit must still exist and be readable.

If ordinary candidates are missing or too few for the required entry count, OneXray may use the first readable active provider configuration by ID in the same scope. Missing latency alone never triggers that fallback. An empty scope may retry all servers; a nonempty scope with too few entries does not expand globally. A successful cross-scope fallback is shown explicitly and changes future connections to Automatic.

Complete configurations are not latency-ranked, combined into entry chains or used as final exits. A fixed ordinary node is not replaced because its latency is unknown or failed. A missing or inactive fixed asset errors; the existing recovery for an active but unreadable ordinary asset may retry global ordinary candidates and reports the fallback. That retry cannot introduce a provider configuration. Fixed personal Raw/provider configurations do not automatically switch to another graph. Cancellation, configuration, compilation, permission and startup failures report their cause instead of trying another provider. Background tests and subscription refreshes never hot-replace a running connection.

Provider and personal Raw JSON

Complete configurations includes personal Raw JSON and subscription-owned provider configurations. Personal Raw is editable; provider originals are read-only and follow their subscription. Both run their own complete graph, without merging App Smart/Custom routing or borrowing ordinary entry nodes.

Use Servers → Add servers → Add Raw JSON to create personal Raw. Selecting a complete graph leaves ordinary route preferences saved. Use previous ordinary plan restores the prior ordinary target after confirmation; cancelling changes nothing. If it is no longer usable, choose a new scope or node. Choices made in other pages or the tray synchronize with Connect.

Runtime and reconnecting

The connection plan and active session are separate. This session combines the actual runtime identity and health information with upload, download, speed and duration in one section. Runtime names, entry chains and final exit come from the actual startup snapshot, not later browsing or renaming.

Before connecting, or when no runtime snapshot is available, the same positions show — placeholders. Old session data is not reused and the plan is not presented as a running connection. Long names stay on one line with an ellipsis; their tooltip shows the full name. This keeps the layout steady as the connection state changes.

Connect shows current-connection speed and traffic, not lifetime totals. Visible pages keep sampling even when a desktop window loses focus; hidden windows and other pages pause sampling. Least-latency multi-chain connections show separate runtime probes, not bandwidth or service-unlock tests.

Changes affecting the active configuration require confirmation and reconnecting. OneXray stops the old VPN, prepares local assets and starts the new runtime. Startup does not download missing routing data. A failure reports the actual cause and does not silently restore the old connection. Page/group question-mark buttons open further help.

Last updated on