mirror of
https://github.com/XTLS/Xray-examples.git
synced 2024-11-21 16:11:32 +00:00
add ENGLISH translate (#133)
* add translate ENGLISH version README.md * Update README.md add link README.ENG.md * Update config_server.json - translation of comments into english * Update config_client.json translation of comments into english * Update config_server.json translation of comments into english * Update config_client.json, translation of comments into english * Update config_server.json translation of comments into english
This commit is contained in:
lk29
GitHub
parent
5ae00c5bb2
commit
cebb145398
|
|
@ -29,10 +29,10 @@
|
|||
"settings": {
|
||||
"servers": [
|
||||
{
|
||||
"address": "example.com", // 你的域名或服务器 IP
|
||||
"flow": "xtls-rprx-direct", // Linux 或安卓可改为 "xtls-rprx-splice"
|
||||
"address": "example.com", // your domain name or server IP
|
||||
"flow": "xtls-rprx-direct", // Linux or android can be changed to "xtls-rprx-splice"
|
||||
"port": 443,
|
||||
"password": "your_password" // 你的密码
|
||||
"password": "your_password" // your password
|
||||
}
|
||||
]
|
||||
},
|
||||
|
|
@ -40,7 +40,7 @@
|
|||
"network": "tcp",
|
||||
"security": "xtls",
|
||||
"xtlsSettings": {
|
||||
"serverName": "example.com" // 你的域名
|
||||
"serverName": "example.com" // your domain name
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@
|
|||
"settings": {
|
||||
"clients": [
|
||||
{
|
||||
"password":"your_password", // 密码
|
||||
"password":"your_password", // password
|
||||
"flow": "xtls-rprx-direct"
|
||||
}
|
||||
],
|
||||
|
|
@ -35,12 +35,12 @@
|
|||
],
|
||||
"certificates": [
|
||||
{
|
||||
"certificateFile": "/path/to/cert", // 证书文件绝对目录
|
||||
"keyFile": "/path/to/key", // 密钥文件绝对目录
|
||||
"ocspStapling": 3600 // 验证周期 3600 秒
|
||||
"certificateFile": "/path/to/cert", // Certificate file absolute directory
|
||||
"keyFile": "/path/to/key", // Key file absolute directory
|
||||
"ocspStapling": 3600 // Verification cycle 3600 Second
|
||||
}
|
||||
],
|
||||
"minVersion": "1.2" // 如果是ecc证书则最低使用 TLSv1.2 ，如果你不清楚证书类型或者不是 ecc 证书，删掉这行
|
||||
"minVersion": "1.2" // If it is an ecc certificate, use TLSv1.2 at least. If you don't know the certificate type or it is not an ecc certificate, delete this line
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
|
|||
16
VLESS-TCP-XTLS-Vision/README.ENG.md
Normal file
16
VLESS-TCP-XTLS-Vision/README.ENG.md
Normal file
|
|
@ -0,0 +1,16 @@
|
|||
:+1:**XTLS Vision [Introduction](https://github.com/XTLS/Xray-core/discussions/1295)**
|
||||
|
||||
**Usage Reminder:**
|
||||
|
||||
:exclamation: Compared with the usage base of XTLS Vision, there are almost no reports of Vision being blocked with **correct configuration**. **Correct configuration** refers to:
|
||||
|
||||
1. The server uses a reasonable port and prohibits traffic returning to China
|
||||
2. Only configure XTLS Vision, not compatible with ordinary TLS proxy
|
||||
3. Fall back to the web page, do not fall back/distribute to other proxy agreements
|
||||
4. Client enables uTLS (fingerprint) [#1](https://github.com/XTLS/Xray-core/issues/1544#issuecomment-1399194727)
|
||||
|
||||
First of all, if you really don't want to be blocked, **please choose a clean IP** first, and build and use XTLS Vision according to **correct configuration**.
|
||||
|
||||
**However, even if you do this, there is no guarantee that you will not be blocked** 100%. Since the end of last year, many people's unknown traffic has been blocked in seconds, and TLS in TLS traffic has been blocked every other day. XTLS Vision is not unknown traffic, and fully handles TLS in TLS features, so far it seems to be effective. **But this does not mean that XTLS Vision can be 100% unblocked. It is very, very important to realize this, and don't make a fuss if you are accidentally blocked**.
|
||||
|
||||
**Because besides the agreement itself, there are many angles that can block you**. Taking IP as an example, you can't guarantee that the IP is really clean, you can't avoid being affected by neighbors, and you can't avoid the entire IP segment being pulled out of the list. It is also possible that GFWs in certain regions have unique standards. For example, if a certain IP has only a few people accessing it, but it can run so much traffic, it will be blocked. **If your XTLS Vision is blocked, but there is no large-scale blocked report like TLS at the end of last year, I sincerely suggest that you change the port, change the IP, and change the service provider to try again**. [#2](https://github.com/XTLS/Xray-core/issues/1544#issuecomment-1402118517)
|
||||
|
|
@ -1,5 +1,7 @@
|
|||
:+1:**XTLS Vision [简介](https://github.com/XTLS/Xray-core/discussions/1295)**
|
||||
|
||||
[ENGLISH](README.ENG.md)
|
||||
|
||||
**使用提醒：**
|
||||
|
||||
:exclamation:相对于 XTLS Vision 的使用基数，目前几乎没有收到 **配置正确** 的 Vision 被封端口的报告，**配置正确** 指的是：
|
||||
|
|
|
|||
|
|
@ -25,8 +25,8 @@
|
|||
},
|
||||
"inbounds": [
|
||||
{
|
||||
"listen": "127.0.0.1", // 填 0.0.0.0 表示允许来自局域网的连接
|
||||
"port": 10808, // v2rayN 本地socks监听端口
|
||||
"listen": "127.0.0.1", // Fill in 0.0.0.0 to allow connections from LAN
|
||||
"port": 10808, // local socks listening port
|
||||
"protocol": "socks",
|
||||
"settings": {
|
||||
"udp": true
|
||||
|
|
@ -40,8 +40,8 @@
|
|||
}
|
||||
},
|
||||
{
|
||||
"listen": "127.0.0.1", // 填 "0.0.0.0" 表示允许来自局域网的连接
|
||||
"port": 10809, // v2rayN 本地http监听端口
|
||||
"listen": "127.0.0.1", // Fill in "0.0.0.0" to allow connections from LAN
|
||||
"port": 10809, // Local http listening port
|
||||
"protocol": "http",
|
||||
"sniffing": {
|
||||
"enabled": true,
|
||||
|
|
@ -58,11 +58,11 @@
|
|||
"settings": {
|
||||
"vnext": [
|
||||
{
|
||||
"address": "", // 地址，服务端的域名或IP
|
||||
"port": 443, // 端口，与服务端一致
|
||||
"address": "", // Address, domain name or IP of the server
|
||||
"port": 443, // Port, consistent with the server
|
||||
"users": [
|
||||
{
|
||||
"id": "", // 用户ID，与服务端一致
|
||||
"id": "", // User ID, consistent with the server
|
||||
"encryption": "none",
|
||||
"flow": "xtls-rprx-vision"
|
||||
}
|
||||
|
|
@ -74,9 +74,9 @@
|
|||
"network": "tcp",
|
||||
"security": "tls",
|
||||
"tlsSettings": {
|
||||
"serverName": "", // SNI，如果"address"填的是服务端的域名，可留空，如果"address"填的是服务端的IP，此处填服务端的证书中包含的域名
|
||||
"serverName": "", // SNI, if "address" is filled with the domain name of the server, it can be left blank. If "address" is filled with the IP of the server, fill in the domain name contained in the certificate of the server here
|
||||
"allowInsecure": false,
|
||||
"fingerprint": "chrome" // 用于配置指定 TLS Client Hello 的指纹，Xray 将通过 uTLS 库 模拟 TLS 指纹，或随机生成
|
||||
"fingerprint": "chrome" // Used to configure the fingerprint of the specified TLS Client Hello, Xray will simulate the TLS fingerprint through the uTLS library, or generate it randomly
|
||||
}
|
||||
},
|
||||
"tag": "proxy"
|
||||
|
|
|
|||
|
|
@ -16,13 +16,13 @@
|
|||
},
|
||||
"inbounds": [
|
||||
{
|
||||
"listen": "0.0.0.0", // "0.0.0.0" 表示同时监听IPv4和IPv6
|
||||
"port": 443, // 服务端监听的端口
|
||||
"listen": "0.0.0.0", // "0.0.0.0" Indicates listening to both IPv4 and IPv6
|
||||
"port": 443, // The port on which the server listens
|
||||
"protocol": "vless",
|
||||
"settings": {
|
||||
"clients": [
|
||||
{
|
||||
"id": "", // 用户ID，执行 xray uuid 生成，或 1-30 字节的字符串
|
||||
"id": "", // User ID, perform xray uuid generation, or a string of 1-30 bytes
|
||||
"flow": "xtls-rprx-vision"
|
||||
}
|
||||
],
|
||||
|
|
@ -48,8 +48,8 @@
|
|||
"certificates": [
|
||||
{
|
||||
"ocspStapling": 3600,
|
||||
"certificateFile": "/etc/ssl/private/fullchain.cer", // 证书文件，建议用fullchain（全SSL证书链），若只有网站证书，会出现v2rayN能使用，v2rayNG不能使用的情况，通常不区分扩展名
|
||||
"keyFile": "/etc/ssl/private/private.key" // 私钥文件
|
||||
"certificateFile": "/etc/ssl/private/fullchain.cer", // For the certificate file, it is recommended to use fullchain (full SSL certificate chain). If there is only a website certificate, v2rayN can be used but v2rayNG cannot be used. Usually, the extension is not distinguished
|
||||
"keyFile": "/etc/ssl/private/private.key" // private key file
|
||||
}
|
||||
]
|
||||
}
|
||||
|
|
@ -76,8 +76,8 @@
|
|||
"policy": {
|
||||
"levels": {
|
||||
"0": {
|
||||
"handshake": 2, // 连接建立时的握手时间限制，单位为秒，默认值为 4，建议与默认值不同
|
||||
"connIdle": 120 // 连接空闲的时间限制，单位为秒，默认值为 300，建议与默认值不同
|
||||
"handshake": 2, // The handshake time limit when the connection is established, in seconds, the default value is 4, it is recommended to be different from the default value
|
||||
"connIdle": 120 // Connection idle time limit in seconds, the default value is 300, it is recommended to be different from the default value
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@
|
|||
"settings": {
|
||||
"clients": [
|
||||
{
|
||||
"id": "", // 填写你的 UUID
|
||||
"id": "", // fill in your UUID
|
||||
"flow": "xtls-rprx-direct",
|
||||
"level": 0,
|
||||
"email": "love@example.com"
|
||||
|
|
@ -18,21 +18,21 @@
|
|||
"decryption": "none",
|
||||
"fallbacks": [
|
||||
{
|
||||
"dest": 1310, // 默认回落到 Xray 的 Trojan 协议
|
||||
"dest": 1310, // Fall back to Xray's Trojan protocol by default
|
||||
"xver": 1
|
||||
},
|
||||
{
|
||||
"path": "/websocket", // 必须换成自定义的 PATH
|
||||
"path": "/websocket", // Must be replaced with a custom PATH
|
||||
"dest": 1234,
|
||||
"xver": 1
|
||||
},
|
||||
{
|
||||
"path": "/vmesstcp", // 必须换成自定义的 PATH
|
||||
"path": "/vmesstcp", // Must be replaced with a custom PATH
|
||||
"dest": 2345,
|
||||
"xver": 1
|
||||
},
|
||||
{
|
||||
"path": "/vmessws", // 必须换成自定义的 PATH
|
||||
"path": "/vmessws", // Must be replaced with a custom PATH
|
||||
"dest": 3456,
|
||||
"xver": 1
|
||||
}
|
||||
|
|
@ -47,8 +47,8 @@
|
|||
],
|
||||
"certificates": [
|
||||
{
|
||||
"certificateFile": "/path/to/fullchain.crt", // 换成你的证书，绝对路径
|
||||
"keyFile": "/path/to/private.key" // 换成你的私钥，绝对路径
|
||||
"certificateFile": "/path/to/fullchain.crt", // Replace with your certificate, absolute path
|
||||
"keyFile": "/path/to/private.key" // Replace it with your private key, absolute path
|
||||
}
|
||||
]
|
||||
}
|
||||
|
|
@ -61,14 +61,14 @@
|
|||
"settings": {
|
||||
"clients": [
|
||||
{
|
||||
"password": "", // 填写你的密码
|
||||
"password": "", // fill in your password
|
||||
"level": 0,
|
||||
"email": "love@example.com"
|
||||
}
|
||||
],
|
||||
"fallbacks": [
|
||||
{
|
||||
"dest": 80 // 或者回落到其它也防探测的代理
|
||||
"dest": 80 // or fall back to other proxies that are also probing-proof
|
||||
}
|
||||
]
|
||||
},
|
||||
|
|
@ -87,7 +87,7 @@
|
|||
"settings": {
|
||||
"clients": [
|
||||
{
|
||||
"id": "", // 填写你的 UUID
|
||||
"id": "", // fill in your UUID
|
||||
"level": 0,
|
||||
"email": "love@example.com"
|
||||
}
|
||||
|
|
@ -98,8 +98,8 @@
|
|||
"network": "ws",
|
||||
"security": "none",
|
||||
"wsSettings": {
|
||||
"acceptProxyProtocol": true, // 提醒：若你用 Nginx/Caddy 等反代 WS，需要删掉这行
|
||||
"path": "/websocket" // 必须换成自定义的 PATH，需要和分流的一致
|
||||
"acceptProxyProtocol": true, // Reminder: If you use Nginx/Caddy to reverse generation WS, you need to delete this line
|
||||
"path": "/websocket" // It must be replaced with a custom PATH, which needs to be consistent with the shunt
|
||||
}
|
||||
}
|
||||
},
|
||||
|
|
@ -110,7 +110,7 @@
|
|||
"settings": {
|
||||
"clients": [
|
||||
{
|
||||
"id": "", // 填写你的 UUID
|
||||
"id": "", // fill in your UUID
|
||||
"level": 0,
|
||||
"email": "love@example.com"
|
||||
}
|
||||
|
|
@ -125,7 +125,7 @@
|
|||
"type": "http",
|
||||
"request": {
|
||||
"path": [
|
||||
"/vmesstcp" // 必须换成自定义的 PATH，需要和分流的一致
|
||||
"/vmesstcp" // It must be replaced with a custom PATH, which needs to be consistent with the shunt
|
||||
]
|
||||
}
|
||||
}
|
||||
|
|
@ -139,7 +139,7 @@
|
|||
"settings": {
|
||||
"clients": [
|
||||
{
|
||||
"id": "", // 填写你的 UUID
|
||||
"id": "", // fill in your UUID
|
||||
"level": 0,
|
||||
"email": "love@example.com"
|
||||
}
|
||||
|
|
@ -149,8 +149,8 @@
|
|||
"network": "ws",
|
||||
"security": "none",
|
||||
"wsSettings": {
|
||||
"acceptProxyProtocol": true, // 提醒：若你用 Nginx/Caddy 等反代 WS，需要删掉这行
|
||||
"path": "/vmessws" // 必须换成自定义的 PATH，需要和分流的一致
|
||||
"acceptProxyProtocol": true, // Reminder: If you use Nginx/Caddy to reverse generation WS, you need to delete this line
|
||||
"path": "/vmessws" // It must be replaced with a custom PATH, which needs to be consistent with the shunt
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
|
|||
Loading…
Reference in a new issue