syscall.SetsockoptInt takes int (Linux) vs syscall.Handle (Windows)
as its first argument. The existing code used int(fd) which fails on
Windows where fd is uintptr and syscall.Handle = uintptr.
Fix: extract a platform-specific setSocketMark(fd uintptr) helper:
- socket_unix.go (!windows) : calls SetsockoptInt(int(fd), ...)
- socket_windows.go (windows): no-op (SO_MARK is Linux-only)
k.GetIntegerValue() returns uint64 on Windows, but proxyEnable was
declared as uint32. Add explicit uint32() conversion to fix the
cross-compilation error:
cannot use k.GetIntegerValue("ProxyEnable") (value of type uint64)
as uint32 value in assignment
Two fixes for the redirect/tproxy interface exclusion feature:
1. Add missing -o/oifname rules for the OUTPUT path
- The TP_RULE chain is jumped from both PREROUTING (tp_pre) and
OUTPUT (tp_out). The existing -i/iifname rules only match the
PREROUTING path correctly (packets arriving on a given interface).
- For the OUTPUT path (locally-originated traffic), the input
interface is always 'lo', so -i never matches the excluded
interface. Add corresponding -o/oifname rules so that locally-
originated traffic going out through an excluded interface is
also bypassed (RETURN before the final REDIRECT/TPROXY action).
- Applies to both redirect and tproxy modes, legacy iptables and
nftables implementations, for both IPv4 and IPv6.
2. Rename nftables set 'interface'/'interface6' to 'local_ips'/'local_ips6'
- These sets store IPv4/IPv6 addresses of local interfaces,
dynamically maintained by the LocalIPWatcher to prevent proxy
loops (traffic destined to local IPs returns early).
- The old name 'interface' was misleading: it suggested it stores
interface names, but the type is ipv4_addr/ipv6_addr.
- The rename affects nftRedirect and nftTproxy, including the
set definitions, chain references (ip daddr @local_ips), and
AddIPWhitelist/RemoveIPWhitelist nft command strings.
core: fix geosite.dat parsing in DNS resolver
- Replace broken GeoSiteList unmarshal with correct varint-length-delimited
stream parser matching xray-core's format
- Add result caching to avoid re-reading the file per tag expansion
service: persist kernel exit status for proper state restoration
- Add LastKernelExitStatus (running/stopped/crashed) to DB
- Set 'running' on graceful shutdown while kernel is active so it
is automatically restored on next startup
- Set 'stopped' when user explicitly stops the kernel via API
- Set 'crashed' when the kernel exits unexpectedly
- Check saved status at startup and log appropriate messages
- Expose lastKernelExit field via GET /api/version for the frontend
- Fix RemoveIPWhitelist table target from mangle to nat in redirect.go
- Fix IsEnabledTproxyWhiteIpGroups() logical operator from && to || in utils.go
- Add whitelist group support for Redirect mode in redirect.go
- Fix data race in LocalIPWatcher by adding sync.Mutex in watcher.go
- Clean up conntrack entries with mark 0x40 on TPROXY teardown in tproxy.go
- Preserve and restore original system proxy state on all platforms (macOS, Windows, Linux)
- Uncomment FakeDNS bypass rules (198.18.0.0/15, fc00::/7) in redirect.go
- Add startup cleanup for residual iptables/nftables rules in transparent.go
The <<< here-string appends an extra newline to the key file, which can
corrupt OpenSSH private key format and cause 'Bad passphrase' errors.
printf writes the exact content of the variable without modification.
The ssh-add_expect (and related expect scripts) were present on disk
but not tracked by git, causing CI to fail with
'No such file or directory' when running the AUR release step.
- Add v2raya_core source downloads and checksums for all architectures
in PKGBUILD and .SRCINFO
- Install v2raya_core to /usr/bin/v2raya_core in package step
- Update deploy_v2raya_bin.sh to compute and substitute v2raya_core hashes
- Fix release workflow: download v2raya_core binaries for hash computation
- Fix release workflow: use heredoc for SSH key to avoid corruption
- Fix release workflow: correct ssh-add_expect script path
- Fix routing rule order: move specific dns-in:53→dns-out rule before
the generic dns-in→direct rule to ensure DNS queries hit dns-out first
- Fix transparent inbound DNS routing: change from direct+geoip:private
to unconditional dns-out for port 53 in tproxy mode
- Add warning log when CouldLocalDnsListen() fails (port 53 conflict)
- Clean up outbound_connections foreign key before deleting from servers in ListRemove
- Preserve user's TproxyExcludedInterfaces setting after FillEmpty defaults
- Add cursor: pointer style to proxy group toggle tag in frontend
Since v2rayA now exclusively uses the v2raya_core binary, simplify or
remove all logic that detected, compared, or branched on different
core types (v2ray, xray, merged).
- Remove CheckCoreVersion, CoreVersionMismatchError, and the
CoreVersion check in StartCoreProcess — core v2raya version
comparison is no longer needed.
- Remove DetectCoreTypeByBinaryName and the Unknown/V2ray/Xray/Merged
variant aliases. The only remaining Variant constant is V2rayaCore.
- Simplify GetV2rayServiceVersion: drop all CoreType/env-config
detection and variant mismatch verification. The function always
returns V2rayaCore and the version string from the binary.
- Simplify CheckV5 / isVersionSatisfied to return only an error,
dropping the unused Variant return value.
- Remove variant-branching in Shadowsocks and Trojan Configuration
methods — both always use the MT (Xray-compatible) path.
- Remove the CheckCoreVersion call from version.go and hardcode
coreVersionValid/ variant in the API response.
- Drop the now-unused where import from shadowsocks.go and trojan.go.
- Update core/xray submodule from v1.260327.0 (v26.3.27) to v26.6.1
- Remove deprecated AllowInsecure field from all protocol structs
- Add PinnedPeerCertSha256 and VerifyPeerCertByName fields (service layer)
- Update ngui (Nuxt) frontend with text inputs for new fields
- Update gui (Vue 2) frontend with text inputs for new fields
- Keep existing PinnedSHA256 for juicity (no duplicate)
- Backward compatible: old allowInsecure params silently ignored
- Run go mod tidy to update dependencies
ProcessManager.Start() now runs resolv/GFWList checks before acquiring
m.mu and defers afterStart (transparent-proxy setup, DNS, TinyTun,
post-start hook) to after the lock is released, eliminating multi-second
lock holds caused by DNS lookups and external hook commands.
TinyTun:
- Fix cancel/stopping ordering race in startTinyTun: assign the new
cancel func before clearing the stopping flag so a concurrent
stopTinyTun always sees the correct cancel
- Resolve proxy-node hostnames concurrently with sync.WaitGroup instead
of sequentially, reducing config-generation latency
- stopTinyTun now waits up to 5 s for the process to exit via a done
channel closed by the monitor goroutine after cmd.Wait() returns
Windows service lifecycle:
- cleanupResources enforces a 30 s hard timeout and adds panic recovery
- HTTP router is shut down before the core process on service stop
- router.Run uses an explicit http.Server + Shutdown() for graceful teardown
Connectivity monitor:
- Extend startup grace period to 15 s on Windows (5 s elsewhere)
- Replace fixed 30 s re-check ticker with exponential back-off (30/60/120 s)
- Probe TinyTun availability via TCP dial to the SOCKS5 port instead of HTTP
Platform guards:
- resolv.CheckResolvConf/WriteResolvConf: no-op on non-Linux
- DNS-hijack operations (NewResolvHijacker, HijackResolv, etc.): Linux-only
On Windows, calling configurev4.IsConfigureNotExists() triggered the v4
library to lazy-initialize using its Linux-default config path (/etc/v2raya).
On Windows, /etc/v2raya resolves to \etc\v2raya on the current drive root
(e.g. C:\etc\v2raya). The v4 library then called os.MkdirAll to create that
directory and bbolt.Open to create boltv4.db inside it -- neither of which
is intentional or useful on Windows.
v2rayA v4 was Linux-only, so no v4 configuration data can ever exist on a
Windows machine. Guard the entire v4 migration check with a runtime.GOOS
check to skip it on Windows.
Also extend sanitizeConfigDirForPlatform to catch the relative-path variant
etc/v2raya (without a leading slash) in addition to the existing check for
the drive-relative /etc/v2raya, providing defence-in-depth if V2RAYA_CONFIG
is ever set to such a value.
When transparent proxy (TinyTun/wintun) is enabled on Windows, the wintun
driver briefly disrupts all traffic while installing routes. This caused
two problems:
1. The connectivity monitor fired its first probe too early, before routes
were fully set up, and received a false network-unavailable result. This
stopped TinyTun prematurely and set networkPaused=true, leaving the
frontend's status tag stuck on the Checking spinner indefinitely.
2. The frontend's /touch request in node.vue created() could fail during
that same disruption window, making the component stay in the loading
state with no retry.
Fixes:
- connectivity.go: add a 5-second startup delay before the first probe so
that wintun has time to finish installing routes.
- node.vue: replace the single /touch call with a retry loop (up to 3
attempts, 2 s apart) that handles both network errors and non-SUCCESS
responses; always sets ready=true after the last attempt to unblock the UI.
- App.vue: call syncLatestNodeOverview() on every WebSocket (re)connect so
the running state is refreshed even if a WS message was missed while the
connection was down.
- Split the single 'V2RAY' tab in gui/modalServer.vue into separate
'VMESS' (tab 0) and 'VLESS' (tab 1) tabs
- Remove the 'Extra Raw JSON' textarea for XHTTP transport and replace
it with complete structured form fields in both tabs:
- Mode, Uplink HTTP Method
- noGRPCHeader / noSSEHeader toggles
- Range config pairs: scMaxEachPostBytes, scMinPostsIntervalMs,
scStreamUpServerSecs, xPaddingBytes, scMaxBufferedPosts
- Full xmux config: maxConcurrency, maxConnections, cMaxReuseTimes,
hMaxRequestTimes, hMaxReusableSecs (all ranges), hKeepAlivePeriod
- Dynamic Custom Headers list (key/value pairs)
- Add XHTTPRangeConfig and XHTTPXmux types to coreObj.go; expand
XHTTPSettings to cover all splithttp proto client fields
- Extend V2Ray struct with 25 new XHTTP fields; update ParseVlessURL,
ExportToURL, and Configuration() accordingly
- Add queryInt / setIntQuery helpers for URL param parsing
- Update all tabChoice indices (+1) for WireGuard through AnyTLS
- Add watch on tabChoice to auto-set v2ray.protocol
Download Linux arm64 service/core artifacts in release_main workflow, package them into v2raya-arm64-linux.zip, generate checksums, and upload to homebrew release assets.
Add a safe statigz handler wrapper that validates fs roots and recovers from FileServer initialization panics.\n\nUse a generic embedded route registrar for /static and /_nuxt with fallback candidates, so both gui and ngui layouts avoid startup panic: open .: file does not exist.
- Wrap /_nuxt/* route registration in fs.Sub() error check
- When _nuxt directory is absent (gui build without ngui),
skip route registration entirely instead of passing an invalid
FS to statigz.FileServer which caused panic on Open('.')
- Add ServerEditor.vue (1864 lines): full server create/edit dialog
supporting 11 protocols (VMess/VLESS/Trojan/SS/SSR/Hysteria2/Juicity/
AnyTLS/TUIC/HTTP/SOCKS5/WireGuard) with Reality protocol parameters
(fp/pbk/sid/spx), URL import/export, and form validation
- Integrate ServerEditor into SubServer.vue with create/edit buttons
and refresh callback
- Rewrite settings page (setting.vue) with ElCollapse panels covering:
GFWList, Transparent Proxy, Routing Rules, Advanced Settings,
Auto-Update, Ports/DNS/CustomInbound/TUN sub-dialogs
- All components use Vue 3 Composition API, Element Plus, and
ngui composables (fetch.ts) for backend API communication
- Add build-with-ngui.sh (Linux) and build-with-ngui.ps1 (Windows)
using pnpm + nuxt generate for ngui frontend
- Configure nuxt.config.ts with nitro.output.publicDir pointing to
service/server/router/web/ for go:embed compatibility
- Add /_nuxt/* route in ServeGUI() to serve Nuxt 3 static assets
alongside existing /static/* route
- Both build systems coexist: build.sh for gui, build-with-ngui.sh for
ngui, Go router handles both
- Xray-core submodule already pointed to v26.3.27 (d2758a02)
- Synchronized go.mod/go.sum dependencies via go mod tidy
- No code changes required: v26.3.23→v26.3.27 has no breaking changes
for Reality protocol
- RealitySettings JSON tags remain fully compatible with Xray-core
v26.3.27 REALITYConfig