The migration wrote each outbound's connected servers and setting into the outbound_connections and outbound_settings tables, while the runtime reads both from system_config under outbound.<name>:connectedServers and outbound.<name>:setting. Every upgrade from a BoltDB release therefore came up with no group members and default outbound settings. The migration now stores the Bolt values under the keys the runtime reads (the ordinals are the ones configure.Which resolves at runtime) and the verification checks those keys. The two tables are gone from the schema; a database that still has them is left alone. The migration also built v2raya.db in place, so an error before the rename left a partial database that made the next start skip the migration and then fail on the remaining bolt.db. It builds a temporary file and renames it in after verification; a bolt.db found next to an existing v2raya.db is moved to a numbered backup instead of blocking every start. The v4 import no longer copies boltv4.db to bolt.db, which produced exactly that pair. A subscription update rewrote the connected ordinals and then replaced the subscription in two commits; they are one transaction.
v2rayA

v2rayA is a V2Ray client supporting global transparent proxy on Linux, Windows and macOS, it is compatible with SS, SSR, Trojan(trojan-go), Tuic and Juicity protocols. [SSR protocol list]
We are committed to providing the simplest operation and meet most needs.
Thanks to the advantages of Web GUI, you can not only use it on your local computer, but also easily deploy it on a router or NAS.
Project:https://github.com/v2rayA/v2rayA
Usage
v2rayA mainly provides the following methods of installation:
- Install from apt-source or AUR
- Docker
- Our self-built scoop bucket (for Windows users)
- Our self-built homebrew tap
- Our self-built OpenWrt repo and OpenWrt's official repo(from OpenWrt version 22.03)
- Microsoft winget: https://winstall.app/apps/v2rayA.v2rayA
- Ubuntu Snap: https://snapcraft.io/v2raya
- Binary file and installation package from GitHub releases
See v2rayA - Docs
Transparent proxy
On Linux, transparent proxy is available as redirect, tproxy or tun; on Windows and macOS as tun or the system proxy.
tun is built into the core: the core opens a TUN device, assigns its address and takes the default route. Its own connections, the direct outbound and the DNS module's upstream queries never enter the TUN (by socket mark on Linux, by binding to the physical interface on Windows and macOS), and every DNS query an application sends to a public resolver is answered by the core's DNS module. v2rayA and the core are always excluded; other processes can be excluded by executable name in the settings. Connected and static routes always bypass the TUN.
Known limitation: on Windows and macOS an application that queries a LAN resolver directly still bypasses the TUN. The system resolver is pointed at the TUN and is covered.
Screenshots
The dashboard: the core, the node in use, live traffic, the transparent proxy and splitting modes, the members' latency and the subscriptions, each a tile.
The RoutingA editor: rules as a list with a rule editor, or as text with line numbers, colouring and per-line checks; the syntax at hand; import and export.
Statement
- The program does not store any user data in the cloud, and all user data is stored in local.
- Do not use this project for illegal purposes.