Commit 0baefc45 (2026-05-03) removed the plugin layer under
service/pkg/plugin and the code that started a plugin per node, but
left the HTTP and ShadowsocksR node types producing what that layer
consumed: a socks outbound to 127.0.0.1:<plugin port> plus a plugin
chain nothing reads. Every http/https proxy node and every SSR node
imported since then connected to a closed local port.
HTTP and HTTPS nodes now produce the core's native http outbound with
the credentials and, for https, TLS to the server name; they no longer
ask for a plugin port. The core has no ShadowsocksR outbound, so an SSR
node's configuration returns an "unsupported" error the latency test
and the automatic selection already understand; the node still parses,
displays and exports so nothing is lost from the store.
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.