Add a subscription with panel Remnawave and choose App-managed nodes or Complete provider configuration. This is available on Servers and Connect without expert mode. Subscription setup.

Response and storage

OneXray accepts complete Xray JSON as one object or a nonempty array. Each valid object is stored separately as type=Remnawave under the same source. The Remnawave panel treats all valid JSON as full-configuration candidates, including outbounds-only objects; only Generic outbounds-only responses use ordinary node parsing. Sing-box JSON is not converted.

After optional age decryption, each complete configuration uses the App adapter and libXray validation. Invalid array members or configurations are skipped without trimming their graph. Both caches are replaced together only when the current mode has usable entries. If all entries fail, OneXray reports a validation error and retains existing data; network, decryption and validation-service failures also leave it unchanged. Valid JSON never falls back to ordinary node parsing.

For a non-JSON Remnawave response, an interactive add or refresh asks whether to convert the source to an ordinary subscription. Confirmation parses the same downloaded plaintext without another request. Only a successful parse saves Generic/App-managed mode with the nodes; URL, User-Agent, age and HWID are retained. Cancelling, parse failure or an automatic refresh without a confirmation context leaves the source and caches unchanged.

A successful complete response also stores ordinary outbounds that can stand alone. Proxies with chain dependencies are not made independent by deleting their references. Switching the subscription mode uses these local caches, without downloading, reconnecting or discarding Smart/Custom preferences. An empty cache asks for refresh; an incompatible fixed selection asks you to select again.

Select and refresh

Open the source and select one complete configuration. The source itself is not an automatic node pool; it cannot supply App entry counts, final exits or ordinary node tests. Provider entries do not use the three-personal-Raw quota.

Refresh follows the normal subscription replacement flow and protects current running, selected and favorite assets. It does not hot-replace a running VPN. View the original JSON or copy it to a personal Raw configuration to edit. A copy is independent of future subscription updates and counts against the Raw quota. Sharing exports an adapted complete Raw copy and any accompanying Geodata links; the saved provider original stays unchanged.

Runtime ownership

The runtime is provider JSON → Remnawave adapter → shared Raw compilation. Existing DNS, routing order, chains, balancers and Observatory are preserved; App Smart/Custom rules, direct-region choices, Fragment, global server-dialing preferences and LAN-sharing listeners are not added. Their preferences remain saved for switching back.

The adapter only supplements the App ingress and necessary system outbounds:

• Reuse tunIn with protocol tun, otherwise the first TUN; normalize its tag and direct inboundTag references. If none exists, prepend a TUN. A new TUN inherits the first SOCKS/HTTP sniffing object when present; existing TUN sniffing stays unchanged. Rules restricted to SOCKS/HTTP ingress gain tunIn.
• Keep existing direct/block tags; append missing freedom/blackhole outbounds.
• Then use the shared VPN supplementation for DNS outbounds and TUN TCP/UDP-53 rules, respecting existing declarations. Newly added provider DNS uses app-remna-dns; forwarding of other query types uses the dedicated direct helper. Missing DNS servers are filled from tunnel settings only at runtime. No generic proxy/direct or DoT catch-all is added.

Shared Raw compilation still manages platform TUN settings, logs, metrics/statistics, resource paths, IPv6 DNS query policy, ports and applicable outbound interfaces. MSIX and the iOS simulator use their platform SOCKS adaptation. The saved original is not the generated runtime JSON. Validation constructs/closes a Core instance; it does not establish VPN connectivity or service access.

Backup

Backup saves the subscription URL, panel/mode and supported credentials, not provider configurations or derived node caches. Refresh the subscription after restoring. A personal Raw copy is backed up as a normal personal asset.