purgatory/Xray-docs-next
1
0
Fork 0
mirror of https://github.com/XTLS/Xray-docs-next.git synced 2025-04-02 21:06:15 +03:00
Code Issues Projects Releases Packages Wiki Activity

Update ch08-xray-clients.md

Browse source
This commit is contained in:
Morrigan-Ship 2025-01-22 01:22:43 +03:30 • committed by GitHub
parent ede029d336
commit 3993be0417
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 140 additions and 149 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

289
docs/en/document/level-0/ch08-xray-clients.md
View file

@ -1,231 +1,222 @@
# 【第 8 章】Xray 客户端篇
# 【Chapter 8】Xray Client Section
## 8.1 Xray 的工作原理简述
## 8.1 Brief Introduction to Xray's Working Principle
要正确的配置和使用`Xray`，就需要正确的理解其工作原理，对于新人，可以先看看下面简化的示意图（省略了许多复杂的设置）：
To properly configure and use `Xray`, you need to understand its working principle. For newcomers, you can first look at the simplified diagram below (many complex settings are omitted):
![Xray数据流向](./ch08-img01-flow.png)
![Xray Data Flow](./ch08-img01-flow.png)
这其中的关键点是：
The key points are:
1. APP 要主动或借助转发工具，将数据【流入(`inbounds`)】`Xray` 客户端
1. The APP must actively, or with the help of forwarding tools, send data `inbounds` to the `Xray` client.
2. 流量进入客户端后，会被【客户端路由(`routing`)】按规则处理后，向不同方向【流出`(outbounds)`】`Xray` 客户端。比如：
2. After traffic enters the client, it will be processed by client routing (`routing`) according to rules and will flow `outbounds` in different directions through the `Xray` client. For example:
1. Domestic traffic is directly connected (`direct`).
2. Foreign traffic is forwarded to VPS (`proxy`).
3. Ad traffic is blocked (`block`).
1. 国内流量直连（`direct`）
2. 国外流量转发 VPS（`proxy`）
3. 广告流量屏蔽（`block`）
3. Foreign traffic forwarded to the VPS bypasses the firewall and `inbounds` into the `Xray` server.
3. 向 VPS 转发的国外流量，会跨过防火墙，【流入(`inbounds`)】 `Xray` 服务器端
4. Once traffic enters the server, just like the client, it will be processed by server routing (`routing`) according to rules and will flow `outbounds` in different directions:
1. Since it is outside the firewall, traffic is directly connected by default, allowing access to previously inaccessible websites (`direct`).
2. If chain forwarding is required between different VPS instances, you can configure forwarding rules (`proxy`).
3. On the server, you can continue to block specific types of traffic, such as ads or BT downloads (`block`).
4. 流量进入服务器端后，与客户端一样，会被【服务器端路由(`routing`)】按规则处理后，向不同方向【流出`(outbounds)`】：
1. 因为已经在防火墙之外，所以流量默认直连，你就可以访问到不存在网站们了（`direct`）
2. 如果需要在不同的 VPS 之间做链式转发，就可以继续配置转发规则（`proxy`）
3. 你可以在服务器端继续禁用各种你想禁用的流量，如广告、BT 下载等（`block`）
:::warning 注意
请务必记得，`Xray` 的路由配置非常灵活，上面的说明只是无限可能性中的一种。
Please remember that `Xray` routing configuration is highly flexible. The explanation above is just one of infinite possibilities.
借助 `geosite.dat` 和 `geoip.dat` 这两个文件，可以很灵活的从【域名】和【IP】这两个角度、不留死角的控制流量流出的方向。这比曾经单一笼统的 `GFWList` 强大很多很多，可以做到非常细致的微调：比如可以指定 Apple 域名直连或转发、指定亚马逊域名代理或转发，百度的域名屏蔽等等。。。）
With the help of `geosite.dat` and `geoip.dat`, you can flexibly control the traffic flow direction from both **domain names** and **IP addresses** perspectives, leaving no blind spots. This is far more powerful than the once simplistic `GFWList`, allowing for precise fine-tuning. For example, you can specify Apple domains for direct connection or forwarding, Amazon domains for proxying or forwarding, Baidu domains for blocking, etc.
Now, [《Brief Analysis of Routing Functionality》](../level-1/routing-lv1-part1.md) is available. I recommend those interested in routing functionality to first complete the basic client configuration explained in this document and then study the detailed information there.
现在，[《路由 (routing) 功能简析》](../level-1/routing-lv1-part1.md) 已经上线，我建议对路由功能有兴趣的同学，先继续跟着本文完成客户端的基础配置，之后再去这里详细学习。
:::
## 8.2 客户端与服务器端正确连接
## 8.2 Proper Connection Between Client and Server
现在你已经理解了 `Xray` 的工作原理，那么接下来的配置，其实就是【告诉你的客户端如何连接 VPS 服务器】。这和你已经很熟悉的、告诉`PuTTY`如何远程连接服务器是一样的。只不过 Xray 连接时的要素不止是【IP 地址】+【端口】+【用户名】+【密码】这四要素了。
Now that you understand the working principle of `Xray`, the next step is to **tell your client how to connect to the VPS server**. This is similar to what you might already be familiar with: telling `PuTTY` how to connect to a server remotely. However, with Xray, the connection involves more than just the four elements of **IP address**, **port**, **username**, and **password**.
实际上，`Xray`的连接要素是由不同的[协议](../../config/inbounds/)决定的。本文在第 7 章的配置文件 `config.json` 里，我们使用 `Xray` 下独特而强大的 `VLESS` 协议 + `XTLS` 流控。所以看看那个配置文件的内容就能知道，这个协议组合的连接要素有：
In fact, the connection elements for `Xray` are determined by the chosen [protocol](../../config/inbounds/). In the configuration file `config.json` from Chapter 7, we used the unique and powerful `VLESS` protocol combined with `XTLS` flow control. By reviewing that configuration file, you can see the connection elements for this protocol combination are:
- 服务器【地址】: `a-name.yourdomain.com`
- 服务器【端口】: `443`
- 连接的【协议】: `vless`
- 连接的【流控】: `xtls-rprx-vision` (vision 模式适合全平台)
- 连接的【验证】: `uuiduuid-uuid-uuid-uuiduuiduuid`
- 连接的【安全】: `"allowInsecure": false`
- Server **Address**: `a-name.yourdomain.com`
- Server **Port**: `443`
- Connection **Protocol**: `vless`
- Connection **Flow Control**: `xtls-rprx-vision` (the vision mode is suitable for all platforms)
- Connection **Authentication**: `uuiduuid-uuid-uuid-uuiduuiduuid`
- Connection **Security**: `"allowInsecure": false`
鉴于新人一般都会使用手机 APP 或者电脑的 GUI 客户端，我就把常用的客户端罗列在下面。每个客户端都有自己独特的配置界面，逐一截图展示并不现实，所以请你务必仔细阅读这些客户端的说明、然后把上述要素填入合适的地方即可。
Since most beginners typically use mobile apps or desktop GUI clients, I have listed the common clients below. Each client has its own unique configuration interface. It is impractical to show screenshots of each one, so please carefully read the documentation for your chosen client and enter the above elements into the appropriate fields.
:::warning 注意
许多工具其实是同时支持 `xray-core` 和 `v2fly-core` 的，但默认内置的不一定是哪个，所以别忘记检查一下是否是你想要的那个在工作哦！
:::warning Notice
Many tools actually support both `xray-core` and `v2fly-core`, but the default built-in core may vary. So, don't forget to check which one is being used to ensure it is the desired one!
:::
- **v2rayN - 适用于 Windows 平台**
- **v2rayN - Suitable for Windows Platform**
- Download the latest version from its [GitHub repository Release page](https://github.com/2dust/v2rayN/releases).
- Follow the instructions provided by the client to configure it.
- 请从它的[GitHub 仓库 Release 页面](https://github.com/2dust/v2rayN/releases)获取最新版
- 请根据该客户端的说明进行设置
- **v2rayNG - Suitable for Android Platform**
- Download the latest version from its [GitHub repository Release page](https://github.com/2dust/v2rayNG/releases).
- Follow the instructions provided by the client to configure it.
- **v2rayNG - 适用于 Android 平台**
- **Shadowrocket - Suitable for iOS and macOS with Apple M chips**
- You need to register a **non-China region** iCloud account.
- Purchase the app from the App Store.
- Follow the instructions provided by the client to configure it.
- 请从它的[GitHub 仓库 Release 页面](https://github.com/2dust/v2rayNG/releases)获取最新版
- 请根据该客户端的说明进行设置
- **Qv2ray - Cross-Platform GUI for Linux, Windows, and macOS**
- Download the latest version from its [GitHub repository Release page](https://github.com/Qv2ray/Qv2ray/releases) (or find newer versions in its [GitHub Actions builds](https://github.com/Qv2ray/Qv2ray/actions)).
- Learn from its [official website](https://qv2ray.net/) documentation.
- Follow the instructions provided by the client to configure it.
- **Shadowrocket - 适用于 iOS, 基于苹果 M 芯片的 macOS**
- **V2RayXS - A macOS Client Based on V2RayX Using xray-core**
- Download the latest version from its [GitHub repository Release page](https://github.com/tzmax/v2rayXS/releases).
- Supports one-click import of [VMessAEAD / VLESS share link standard proposal](https://github.com/XTLS/Xray-core/issues/91) compliant sharing links.
- Follow the instructions provided by the client to configure it.
- 你需要注册一个【非中国区】的 iCloud 账户
- 你需要通过 App Store 搜索并购买
- 请根据该客户端的说明进行设置
At this point, your full configuration should be working properly!
- **Qv2ray - 跨平台图形界面，适用于 Linux, Windows, macOS**
## 8.3 Bonus Question 1: Manually Configuring `xray-core` on PC
- 请从它的[GitHub 仓库 Release 页面](https://github.com/Qv2ray/Qv2ray/releases)获取最新版（还可以从它的[GitHub 自动构建仓库](https://github.com/Qv2ray/Qv2ray/actions)寻找更新的版本）
- 请从它的[项目主页](https://qv2ray.net/)学习文档
- 请根据该客户端的说明进行设置
Although the previous step is sufficient to complete the setup, if you're a curious and attentive learner, you may recall that I mentioned in the last chapter: "If you place the `xray-core` binary on the server and run it, it becomes the server side; if you download it and run it on your local computer, it becomes the client side." So how exactly do you use `xray-core` as a client directly?
- **V2RayXS - 基于 V2RayX 开发的一款使用 xray-core 的 macOS 客户端**
- 请从它的 [GitHub 仓库 Release 页面](https://github.com/tzmax/v2rayXS/releases) 获取最新版
- 支持一键导入 [VMessAEAD / VLESS 分享链接标准提案](https://github.com/XTLS/Xray-core/issues/91) 为标准的分享链接
- 请根据该客户端的说明进行设置
To answer this question, I’ve added a bonus section. It’s a bit beyond the scope and a little more troublesome, but I’m explaining it because this method has some advantages:
到这一步，你的全套配置就已经可以正常使用啦！
- Get the latest version immediately without waiting for the app to update.
- Flexible and free routing configuration capabilities (of course, the advanced routing editor in the GUI client Qv2ray is very powerful and can fully implement the routing configuration of xray-core).
- Save system resources (GUI interfaces always consume resources, and the amount of consumption depends on how the client is implemented).
## 8.3 附加题 1：在 PC 端手工配置 `xray-core`
Its disadvantage is that it requires **manually writing configuration files**, which can be a bit troublesome. But honestly, think about it: you’ve already successfully written the configuration on the server once. What’s the difference now? Let’s break down the steps as usual:
虽然到上面一步已经可以结束了，但是如果你是个好奇心强、记忆力好的的同学，一定会想起来我在上一章说过，你把`xray-core` 的二进制文件“放在服务器运行，它就是服务器端；你把它下载到本地电脑运行，它就是客户端。” 那究竟要怎样直接使用 `xray-core` 做客户端呢？
为了回答这个问题，我加入了附加题章节，有一点点超纲，有一点点麻烦，但费这个笔墨是因为这个方式有它的优势：
- 第一时间获得最新版而无需等待 APP 升级适配
- 灵活自由的路由配置能力（当然 GUI 客户端中 Qv2ray 的高级路由编辑器非常强大，也可以完整实现 xray-core 的路由配置功能）
- 节约系统资源 （GUI 界面一定会有资源消耗，消耗的多少则取决于客户端的实现）
它的劣势应该就是【需要手写配置文件】有点麻烦了。但其实，你想想，服务器上你已经成功的写过一次了，现在又有什么区别呢？接下来，还是老样子，我们分解一下步骤：
1. 首先请从 Xray 官方的 [GitHub 仓库 Release 页面](https://github.com/XTLS/Xray-core/releases) 获取对应平台的版本，并解压缩到合适的文件夹
2. 在合适的文件夹建立空白配置文件：`config.json` （自己常用平台下新建文件大家肯定都会，这就真不用啰嗦了）
3. 至于什么是“合适的文件夹”？这就取决于具体的平台了~
4. 填写客户端配置
- 我就以 `8.1` 原理说明里展示的基本三类分流（国内流量直连、国际流量转发 VPS、广告流量屏蔽），结合 `8.2` 的连接要素，写成一个配置文件
- 请将 `uuid` 替换成与你服务器一致的 `uuid`
- 请将 `address` 替换成你的真实域名
- 请将 `serverName` 替换成你的真实域名
- 各个配置模块的说明我都已经（很啰嗦的）放在对应的配置点上了
1. First, download the appropriate version for your platform from the official Xray [GitHub repository Release page](https://github.com/XTLS/Xray-core/releases) and extract it to a suitable folder.
2. In the chosen folder, create an empty configuration file: `config.json` (you surely know how to create a new file on your commonly used platform, so no need to elaborate here).
3. As for what is a “suitable folder”? It depends on the specific platform~
4. Fill in the client configuration:
- I’ll write a configuration file based on the basic three types of traffic routing displayed in `8.1` (domestic traffic direct connection, international traffic forwarded to VPS, ad traffic blocking), combined with the connection elements from `8.2`.
- Replace `uuid` with the same `uuid` as your server.
- Replace `address` with your actual domain name.
- Replace `serverName` with your actual domain name.
- I’ve already (quite extensively) explained each configuration module at the corresponding configuration point.
```json
// REFERENCE:
// https://github.com/XTLS/Xray-examples
// https://xtls.github.io/config/
// 常用的config文件，不论服务器端还是客户端，都有5个部分。外加小小白解读：
// ┌─ 1_log 日志设置 - 日志写什么，写哪里（出错时有据可查）
// ├─ 2_dns DNS-设置 - DNS怎么查（防DNS污染、防偷窥、避免国内外站匹配到国外服务器等）
// ├─ 3_routing 分流设置 - 流量怎么分类处理（是否过滤广告、是否国内外分流）
// ├─ 4_inbounds 入站设置 - 什么流量可以流入Xray
// └─ 5_outbounds 出站设置 - 流出Xray的流量往哪里去
// Standard config file structure (server/client) with 5 core components:
// ┌─ 1_log Logging - What/Where to log (troubleshooting)
// ├─ 2_dns DNS - How to resolve domains (anti-pollution, privacy)
// ├─ 3_routing Traffic routing - How to classify traffic (ad-blocking, geo-routing)
// ├─ 4_inbounds Inbound rules - Acceptable incoming traffic
// └─ 5_outbounds Outbound rules - Where to forward traffic
{
// 1_日志设置
// 注意，本例中我默认注释掉了日志文件，因为windows, macOS, Linux 需要写不同的路径，请自行配置
// 1_Log Settings
// Log paths commented for cross-platform compatibility (configure manually)
"log": {
// "access": "/home/local/xray_log/access.log", // 访问记录
// "error": "/home/local/xray_log/error.log", // 错误记录
"loglevel": "warning" // 内容从少到多: "none", "error", "warning", "info", "debug"
// "access": "/home/local/xray_log/access.log", // Access logs
// "error": "/home/local/xray_log/error.log", // Error logs
"loglevel": "warning" // Levels: "none", "error", "warning", "info", "debug"
},
// 2_DNS设置
// 2_DNS Settings
"dns": {
"servers": [
// 2.1 国外域名使用国外DNS查询
// 2.1 Foreign domains → Foreign DNS
{
"address": "1.1.1.1",
"domains": ["geosite:geolocation-!cn"]
},
// 2.2 国内域名使用国内DNS查询，并期待返回国内的IP，若不是国内IP则舍弃，用下一个查询
// 2.2 Chinese domains → Chinese DNS (CN IPs only)
{
"address": "223.5.5.5",
"domains": ["geosite:cn"],
"expectIPs": ["geoip:cn"]
},
// 2.3 作为2.2的备份，对国内网站进行二次查询
// 2.3 Fallback for Chinese domains
{
"address": "114.114.114.114",
"domains": ["geosite:cn"]
},
// 2.4 最后的备份，上面全部失败时，用本机DNS查询
// 2.4 Final fallback → Local DNS
"localhost"
]
},
// 3_分流设置
// 所谓分流，就是将符合否个条件的流量，用指定`tag`的出站协议去处理（对应配置的5.x内容）
// 3_Routing Rules
"routing": {
"domainStrategy": "IPIfNonMatch",
"rules": [
// 3.1 广告域名屏蔽
// 3.1 Block ads
{
"type": "field",
"domain": ["geosite:category-ads-all"],
"outboundTag": "block"
},
// 3.2 国内域名直连
// 3.2 Direct connect Chinese domains
{
"type": "field",
"domain": ["geosite:cn"],
"outboundTag": "direct"
},
// 3.3 国外域名代理
// 3.3 Proxy foreign domains
{
"type": "field",
"domain": ["geosite:geolocation-!cn"],
"outboundTag": "proxy"
},
// 3.4 走国内"223.5.5.5"的DNS查询流量分流走direct出站
// 3.4 Direct route DNS queries to 223.5.5.5
{
"type": "field",
"ip": ["223.5.5.5"],
"outboundTag": "direct"
},
// 3.5 国内IP直连
// 3.5 Direct connect Chinese IPs
{
"type": "field",
"ip": ["geoip:cn", "geoip:private"],
"outboundTag": "direct"
}
// 3.6 默认规则
// 在Xray中，任何不符合上述路由规则的流量，都会默认使用【第一个outbound（5.1）】的设置，所以一定要把转发VPS的outbound放第一个
// 3.6 Default: First outbound (5.1)
]
},
// 4_入站设置
// 4_Inbound Settings
"inbounds": [
// 4.1 一般都默认使用socks5协议作本地转发
// 4.1 Default SOCKS5 proxy
{
"tag": "socks-in",
"protocol": "socks",
"listen": "127.0.0.1", // 这个是通过socks5协议做本地转发的地址
"port": 10800, // 这个是通过socks5协议做本地转发的端口
"listen": "127.0.0.1", // SOCKS5 local address
"port": 10800, // SOCKS5 local port
"settings": {
"udp": true
}
},
// 4.2 有少数APP不兼容socks协议，需要用http协议做转发，则可以用下面的端口
// 4.2 HTTP proxy (for SOCKS-incompatible apps)
{
"tag": "http-in",
"protocol": "http",
"listen": "127.0.0.1", // 这个是通过http协议做本地转发的地址
"port": 10801 // 这个是通过http协议做本地转发的端口
"listen": "127.0.0.1", // HTTP proxy address
"port": 10801 // HTTP proxy port
}
],
// 5_出站设置
// 5_Outbound Settings
"outbounds": [
// 5.1 默认转发VPS
// 一定放在第一个，在routing 3.6 里面已经说明了，这等于是默认规则，所有不符合任何规则的流量都走这个
// 5.1 Primary proxy (MUST be first)
{
"tag": "proxy",
"protocol": "vless",
"settings": {
"vnext": [
{
"address": "a-name.yourdomain.com", // 替换成你的真实域名
"address": "a-name.yourdomain.com", // Your domain
"port": 443,
"users": [
{
"id": "uuiduuid-uuid-uuid-uuid-uuiduuiduuid", // 和服务器端的一致
"id": "uuiduuid-uuid-uuid-uuid-uuiduuiduuid", // Match server ID
"flow": "xtls-rprx-vision",
"encryption": "none",
"level": 0
@ -238,18 +229,18 @@
"network": "tcp",
"security": "tls",
"tlsSettings": {
"serverName": "a-name.yourdomain.com", // 替换成你的真实域名
"allowInsecure": false, // 禁止不安全证书
"fingerprint": "chrome" // 通过 uTLS 库 模拟 Chrome / Firefox / Safari 或随机生成的指纹
"serverName": "a-name.yourdomain.com", // Your domain
"allowInsecure": false, // Disallow insecure certs
"fingerprint": "chrome" // uTLS fingerprint spoofing
}
}
},
// 5.2 用`freedom`协议直连出站，即当routing中指定'direct'流出时，调用这个协议做处理
// 5.2 Direct connection
{
"tag": "direct",
"protocol": "freedom"
},
// 5.3 用`blackhole`协议屏蔽流量，即当routing中指定'block'时，调用这个协议做处理
// 5.3 Traffic blocking
{
"tag": "block",
"protocol": "blackhole"
@ -258,76 +249,76 @@
}
```
## 8.4 附加题 2：在 PC 端手工运行 `xray-core`
## 8.4 Additional Task 2: Manually Run `xray-core` on PC
写好了配置文件该，要怎么让 `xray-core` 运行起来呢？双击好像并没有反应啊？
After creating the config file, how do I make `xray-core` run? Double-clicking doesn't seem to work?
首先，你要找到电脑上的【命令行界面】。
First, locate your computer's **Command Line Interface**.
1. Linux 桌面、macOS 系统的同学肯定已经比较熟悉了，搜索 `Console` 或者 `Terminal` 就可以
2. Windows 就可以搜索使用 `Cmd` 或者 `Powershell` 等程序（WSL 的同学你坐下，你的 `Console` 当然也可以）
1. **Linux Desktop/macOS** users: Search for `Console` or `Terminal`
2. **Windows** users: Use `Cmd` or `Powershell` (WSL users: Your `Console` works too)
其次，我们要做的事情是【让 `xray` 找到并读取配置文件 `config.json`，然后运行】，所以：
Secondly, what we need to do is [let `xray` find and read the configuration file `config.json`, and then run], so:
1. 在 Windows 下，假设你的 `Xray` 程序位置是 `C:\Xray-windows-64\xray.exe`，配置文件位置是`C:\Xray-windows-64\config.json`，那么正确的启动命令就是：
1. Under Windows, assuming your `Xray` program location is `C:\Xray-windows-64\xray.exe` and the configuration file location is `C:\Xray-windows-64\config.json`, then the correct startup command is:
```shell
C:\Xray-windows-64\xray.exe -c C:\Xray-windows-64\config.json
```
:::tip 说明
这里的 `-c` 就是指定配置文件路径的参数，告诉 `xray` 去后面的位置找配置文件
:::tip
Here, `-c` is a parameter that specifies the path of the configuration file, telling `xray` to look for the configuration file in the following location
:::
2. 相似的，在 Linux 和 macOS 下，假设你的 `Xray` 程序位置是 `/usr/local/bin/xray`，配置文件位置是`/usr/local/etc/xray/config.json`，那么正确的启动命令就是
2. Similarly, under Linux and macOS, assuming your `Xray` program location is `/usr/local/bin/xray` and the configuration file location is `/usr/local/etc/xray/config.json`, then the correct startup command is:
```shell
/usr/local/bin/xray -c /usr/local/etc/xray/config.json
```
:::tip 说明
每个系统都有系统路径变量，所以写 `Xray` 程序时不一定要写绝对路径。但是写了肯定没错，所以我就如此演示了。
:::tip
Every system has a system path variable, so you don't have to write the absolute path when writing the `Xray` program. But it's definitely correct, so I demonstrated it this way.
:::
## 8.5 附加题 3：在 PC 端开机自动运行 `xray-core`
## 8.5 Additional question 3: Automatically run `xray-core` on the PC
如果你真的尝试了手动运行 `xray-core`，你一定会发现这个方式还有点小问题：
If you actually try to run `xray-core` manually, you will find that there are some minor issues with this approach:
1. 每次运行 `Xray` 都要出现一个黑乎乎的窗口，很丑
2. 不能开机自动运行，每次都要手工输入，十分不方便
1. Every time I run `Xray`, a black window appears, which is ugly
2. It cannot be started automatically, and I have to enter it manually every time, which is very inconvenient
我可以肯定的告诉你：**完全可以解决**。但是具体的解决方式，就当作课外作业留给大家吧！（友情提示，文档站的问答区有线索哦）
I can tell you for sure: **It can be solved**. But the specific solution is left as an extracurricular homework! (Friendly reminder, there are clues in the Q&A area of ​​the document site)
## 8.6 圆满完成！
## 8.6 Completed successfully!
我相信，有耐心看到这里的同学，都是兼具好奇心和行动力的学习派！我现在要郑重的恭喜你，因为到了这里，你已经完完整整的【**从第一条命令开始，完成了 VPS 服务器部署，并成功的在客户端配置使用 Xray**】了！这毫无疑问是一个巨大的胜利！
I believe that the students who have the patience to see this are all curious and motivated learners! I would like to congratulate you now, because at this point, you have completed the VPS server deployment from the first command, and successfully configured and used Xray on the client**! This is undoubtedly a huge victory!
我相信，你现在一定对`Linux`不再恐惧，对`Xray`不再陌生了吧！
I believe that you must no longer be afraid of `Linux` and no longer unfamiliar with `Xray`!
**至此，小小白白话文圆满结束！**
**So far, the little white text has ended successfully! **
> ⬛⬛⬛⬛⬛⬛⬛⬛ 100%
## 8.7 TO INFINITY AND BEYOND!
**但现在你看到的，远远不是 Xray 的全貌。**
**But what you see now is far from the full picture of Xray.**
`Xray` is a powerful and rich collection of network tools. It provides many modules on a platform. It can solve various problems through flexible configuration combinations like a Swiss Army Knife. In this article, I just used the **simplest** and **most intuitive** configuration to do **basic demonstration**.
`Xray`是一个强大而丰富的网络工具集合，平台化的提供了众多模块，可以像瑞士军刀一样，通过灵活的配置组合解决各种不同的问题。而本文，仅仅蜻蜓点水的用了**最简单**、**最直观**的配置来做**基础演示**。
If you think it is enough now, then enjoy the information freedom it brings you. But if your curiosity still can't stop, then continue to explore its infinite possibilities!
如果你觉得现在已经完全够用了，那就好好的享受它给你带来的信息自由。但如果你的好奇心依然不能停歇，那就去继续挖掘它无限的可能性吧！
For more information, you can find it here:
需要更多信息，可以到这里寻找：
1. [xtls.github.io](https://xtls.github.io/) - 官方文档站
2. [官方 Telegram 群组](https://t.me/projectXray) - 活跃而友善的官方讨论社区
1. [xtls.github.io](https://xtls.github.io/en/) - Official Documentation Site
2. [Official Telegram Group](https://t.me/projectXray) - friendly official discussion community
![TO INFINITY AND BEYOND!](./ch08-img02-buzz.png)
:::tip 不算后记的后记
希望我陪你走过的这一段小小的旅程，可以成为你网络生活中的一份小小助力。
这篇文章里的工具和信息难免会一点点的陈旧过时，但你一定会逐渐成长为大佬。未来的某个时间，若你能偶尔想起这篇教程、想起我写下本文的初衷，那我衷心希望你能够薪火相传、把最新的知识分享给后来人，让这一份小小的助力在社区里坚定的传递下去。
这是个大雪封山乌云密布的世界，人们孤独的走在各自的路上试图寻找阳光，如果大家偶尔交汇时不能守望相助互相鼓励，那最终剩下的，恐怕只有【千山鸟飞绝 万径人踪灭】的凄凉了吧。
:::
tip (An afterword that is not really an afterword)
I hope that this little journey I have taken with you can be a small help in your online life.
The tools and information in this article will inevitably become outdated, but you will gradually grow into a big guy. Sometime in the future, if you can occasionally remember this tutorial and the original intention of writing this article, then I sincerely hope that you can pass on the torch and share the latest knowledge with the next generation, so that this little help can be firmly passed on in the community.
This is a world with heavy snow and dark clouds. People walk alone on their own roads trying to find sunshine. If everyone can't help and encourage each other when they occasionally meet, then in the end, I am afraid that only the desolation of [the birds have flown away from the thousands of mountains and the people have disappeared on the thousands of paths] will be left.
:::