WinXray Getting Started Tips WinXray Related Video List Network Free vmess Server Subscription Link Network Free Shadowsocks Server Subscription Link Network Free Clash Server Subscription Link Copy the subscription links in various formats above and experience winXray with strong compatibility by clicking on "Bulk Import Links" in winXray. The free server is for testing only (be sure to go PAC, don't open a global agent don't log in to your account, and don't use it for long periods of time).
winXray WinXray🔊 is the most compact and light V2Ray, XRay, Trojan, Trojan-go, Shadowsocks, SSR, SSRoT, NaïveProxy, SOCKS, HTTP, HTTPS All-in-One Universal Client (Windows system), which enables concurrent detection of a large number of servers and quickly finds the fastest servers today, automatically looks for other fastest servers when connected to anomalies - switching as fast as lightning, automatically refreshing subscriptions when server exceptions are obtained from a feed, and automatically deploying server-side tools with one click.
The software source has waived copyright contribution to the public domain, the source code can use aardio compilation to generate a single file green EXE, click here to download (64-bit version / 32-bit version), unzip can be used directly (small size only 6.1 MB - has come with V2Ray Core).
Must read before use Finally have to delete the library to run the reason why everyone understands not to have to say more about me?! I deleted the library very quickly because I wrote the code so fast, I took a few hours to complete winXray's main code, and in a few days the upgrade quickly reached the maturity of the average other software written for several years! Because I'm about to delete the library, but I'm pushing up the update - fork's projects are basically not as quick as the active pull update, you can see winXray online just a few days after more than 600 forks, so if I push the update before not deleting the library, then I delete the library after no one can find the latest version of the source code.
Now most antivirus software is whitelisted to kill, so the new EXE will be falsely reported virus, because I update too fast, so constantly push the new EXE up, so you may encounter false positives, but you can fully use the source code to compile their own exact same EXE, and some people boast that other wall-turning software does not false positives - you go to the problems and online search how many false positives good or bad?! Encounter false positives can be submitted to your antivirus vendor for verification, or you can compile your own source code to generate EXE after use, solve and verify the problem is easy - other sets are redundant.
Originally winXray source has given up copyright contribution to the public domain, but someone (TheMRLL) took the source code to drag a big and ugly promotion button on, nothing to release a new version of the self-proclaimed official, but also the source code I was shocked to find that there were such shameless people in the world by vilifying the author (misinformation could not read the self-proclaimed open source software official) and by blocking and threatening posts that referred to the original winXray. Originally is to give you free to play, eat so ugly conscience will not hurt?! Originally I wanted to change a license to limit this bad behavior, but in the end I decided to continue to give up copyright, continue to contribute the source code to the public domain, that is, open source, we must be open thoroughly, we can not because there are individual villains in the world and give up their own good intentions.
It has recently been discovered that TheMRLL has some very strange behavior. Every time I release a new version, he copies and pastes it later and then reissues it, and even more curiously, his commits are basically fake, and I checked with the file comparison tool that many of his so-called improvements have simply added empty functions (and double-clicking on the sample code generated by the controls in the development tool). Also he doesn't know why a lot of code is misplaced when copying and pasting, so he provides a lot of weird BUGs for the program - these are not the originals I provided. While I'm not against the free use of winXray's source code, this MRLL is so unspeady that the EXE he offers please be careful about downloading it safely.
PAC Agent Mode / Global Agent - Routing Mode Comparison WinXray's PAC agents are stable, fluid, and easy to use. In PAC mode, winXray prioritizes the efficient and secure SOCKS5 protocol and is automatically compatible with apps that only support HTTP agents in PAC mode. WinXray also provides perfect support for telegram IP address libraries in PAC mode.
SOCKS5 supports comparison:
Global routing mode: SOCKS5 is not supported PAC mode: Supports SOCKS5 for efficient and secure security UWP app support comparison:
Global routing mode: None of the UWP apps can be networked. PAC mode: UWP apps can be networked normally, and local agents can be turned on for UWP apps using winXray's Own Tool. DNS resolution comparison:
Global routing patterns: Using this native to initiate DNS resolution returns the address that applies to the domestic line, even if set to a foreign DNS server. PAC mode: Secure and reliable using DNS resolution on the server. Automatically switch agent protocols based on the client:
Global routing mode: Not supported PAC mode: PAC agents in winXray give priority to efficient and secure SOCKS5 proxy protocols for target apps, such as browsers, and winXray automatically provides HTTP agents for those apps in PAC mode for apps that do not support SOCKS agents, such as Google Earth. IP segment proxy rules:
Global routing patterns: Better support for IP segment proxy rules PAC mode: WinXray PAC can support IP segment proxy rules (perfect support for Telegram). independence
Global routing patterns: Not independent, proxy rules are integrated into the wall-turning software kernel PAC mode: Completely independent, PAC proxy services are completely independent of wall-turning software, and only PAC-specified domain names or IPs interact with wall-over software. compatibility
Global routing pattern: Not a rule implemented by the system, once the global agent is set up, regardless of whether the appropriate software is not suitable for the agent is forced to use the agent, so compatibility is not very good, resulting in the above UWP can not network and other issues. PAC mode: The PAC provided by the system has good compatibility, because the history is long, the general software will have good compatibility with the PAC, PAC is mainly suitable for the agent browser and other software design, so other software can better identify and judge whether to use the PAC designated agent or direct connection. Simplicity
Global routing patterns: Complex configuration with a certain threshold. PAC mode: The configuration is very simple. It is generally not recommended for regular users to edit routing rules - misconfiguration can cause sensitive traffic to go to the proxy server by mistake. Professional things should be left to professionals, using winXray to enable and update the latest routing rules provided by v2ray-rules-dat with one click.
Note That in winXray, SSRoT supports V2Ray routing rules regardless of whether you use NaïveProxy or SSR.
What if the system agent fails If setting up an agent doesn't work properly later: first right-click on the tray icon of the winXray taskbar, click View Internet Agent Settings in the pop-up right-click menu, and check that the agent settings are working. If winXray cannot modify the proxy settings, but can modify them manually successfully, this is generally blocked by the security software incorrectly (and the security software does not pop up the confirmation dialog box properly, or the block settings are incorrect). At this point, add winXray to the trust list in the relevant settings of the security software.
If it's not for the reason above, press the Win-R key combination to open the system run dialog box, enter regedit click OK to open the registry path HKEY_CURRENT_USER
If the above method still doesn't work, open the open path computer in the registry, HKEY_LOCAL_MACHINE system, CurrentControlSet, Services, WinHttp AutoProxySvc, change the value of start to 2, that is, change the WinHttp AutoProxySvc service to start automatically, and then restart the computer.
Core default path: Update V2Ray Core / Xray Core / SSR Core can be downloaded in WinXray/Configuration /Core Configuration, and the V2Ray core is automatically switched after downloading update V2Ray Core (or Xray Core).
V2Ray Core (or Xray Core) is found by default in the following directory:
./v2ray-core/ %localappdata%\winXray\core SSR Core is found by default in the following directories:
./v2ray-core/ssr-core %localappdata%\winXray\ssr-core By default, naïveProxy Core is found in the following directory:
./v2ray-core/naive-core %localappdata%\winXray\naive-core Can't find automatic download, no agent access to Github will be slow, sometimes may not open at all, it is recommended to run often winXray tool comes with the "Github network speed optimization tool"
Note that different proxy protocol connections will call different Cores, such as NaïveProxy connection will start the naive .exe, this time the system firewall will be prompted, if this time did not see the point of rejection, then can not use the corresponding Core normally, so please see clearly again, point wrong to the system firewall and then open it.
Install the NaïveProxy service Reference:https://github.com/klzgrad/naiveproxy Take CentOS as an example:
yum intall golang yum install git go get -u github.com/caddyserver/xcaddy/cmd/xcaddy ~/go/bin/xcaddy build --with github.com/caddyserver/forwardproxy@caddy2=github.com/klzgrad/forwardproxy@naive sudo setcap cap_net_bind_service=+ep ./caddy wget -O naive.tar.xz https://github.com/klzgrad/naiveproxy/releases/download/v88.0.4324.96-1/naiveproxy-v88.0.4324.96-1-linux-x64.tar.xz tar -xf ./naive.tar.xz
mv naiveproxy-v88.0.4324.96-1-linux-x64 naive echo -e "{\n "listen": "socks://127.0.0.1:1080",\n "proxy": "https://user:pass@example.com\"\n}" > ./naive/config.json
cat << EOF > ./Caddyfile :443, example.com tls me@example.com route { forward_proxy { basic_auth user pass hide_ip hide_via probe_resistance } file_server { root /var/www/html } } EOF
iptables -A INPUT -p tcp --dport 80 -j ACCEPT;iptables -A INPUT -p tcp --dport 443 -j ACCEPT;firewall-cmd --permanent --add-port=80/tcp;firewall-cmd --permanent --add-port=443/tcp;firewall-cmd --reload;
./naive/naive --config ./naive/config.json & ./caddy run # 后台运行改成 ./caddy start Before you install, you need to prepare a domain name in advance and replace the example.com in the script above with your domain name, user:pass instead of the proxy login username and password.