Skip to content
Servers

Servers

Browse Nodes, Complete configurations and Subscriptions in separate categories, with full-page details. Servers are organized by subscription and manual groups. There is no location tab or exit-region detection. Smart Routing’s direct-region setting and GeoData remain available.

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.

Groups and types

Subscriptions keep their ID order. Manually added ordinary nodes can be organized into one level of named groups, with Ungrouped first and empty custom groups retained. Ordinary rows show type=outbound, protocol/transport/security and latency; complete subscription configurations show type=Remnawave and are selected individually. They do not enter ordinary node tests or entry/exit pools.

Create or rename a manual group and use a node’s Move to group action to change membership. New imports and local copies append to Ungrouped. Dissolve group keeps its nodes and appends them to Ungrouped; Delete group and servers asks for confirmation and handles any selected or running nodes. Moving preserves configuration, favorite status and latency without reconnecting.

Custom manual groups organize browsing and management; they are not separate automatic connection pools. All manual servers still includes every group, and a node can be selected individually. Raw and provider configurations do not join manual groups. App-managed subscriptions can supply a group or fixed node; provider-managed subscriptions support explicit selection and the documented automatic fallback to one complete configuration. Subscription modes.

Manual order and display sorting

The main node list offers Arrange node order when search is empty, the favorites filter is off and the source is All or manually added nodes. Choose a complete nonempty manual group if needed. Name/Latency display sorting does not hide this action; arranging loads saved manual positions and only saves the chosen whole group.

Open the group-order or server-order page to arrange custom groups or nodes within one manual group. Long-press the handle on mobile, drag it on desktop, or use the up/down buttons. Save commits the draft; Back or Cancel discards it. Clear search before arranging. Cross-group dragging is not supported; use Move to group instead. If membership changes, reload the ordering draft.

Sort servers offers Default order, Name, or Latency. Default keeps subscription ID order and saved manual group/node positions. Name ignores case and surrounding spaces. Latency places successful results fastest first, then untested, failed, and provider complete configurations; ties use ID order. Name/latency sorting does not overwrite manual positions; switching back to Default shows them again.

Display sorting is saved on this device and shared with final-exit selection and desktop tray lists. Search and favorites keep the chosen order; subscription group order is unchanged. Manual groups and positions are included in connection backups, while the display-sort preference is not. Neither sorting nor arranging changes connection-candidate ranking or moves a running connection. Successful cached latencies rank first for automatic selection; missing or failed results do not make a node unusable.

Latency and actions

Fast means up to 500 ms, Slow up to 1000 ms, and Available above 1000 ms. Untested, failed and timed-out states are separate. These are HTTP test results, not bandwidth or service-unlock guarantees.

Nodes support edit, favorite, share and delete. Complete provider configurations are read-only: view JSON, select, favorite, share, delete, or copy to personal Raw JSON for editing. The copy uses the personal Raw limit; subscription configurations do not. Complete configurations have their own favorites filter for provider entries. Personal Raw JSON cannot be favorited.

Test servers in the main node list takes a snapshot of the current source, search and favorites filters and tests only the matching testable ordinary nodes. It does not change the connection selection. You can change filters and still cancel the original request; cancellation keeps completed results, waits for the current batch and skips subsequent batches.

Manual tests of a node or App-managed subscription warn when VPN can affect the result. The subscription or group detail action changes from Test to Cancel, then Cancelling. Repeated clicks do not submit the same request again. Cancellation skips that source’s pending batches, lets the current batch finish and leaves other sources and VPN running. Latency settings.

Add servers · Remnawave configurations

Last updated on