Max/XTLS_Xray-docs-next
1
0
Fork 0
mirror of https://github.com/XTLS/Xray-docs-next.git synced 2026-09-30 10:58:12 +03:00
Code Issues Packages Projects Releases Wiki Activity

Infra/conf: Rename inbounds clients to users

Browse Source
This commit is contained in:
Meow
2026-05-06 12:25:52 +08:00
parent 64d0e2c213
commit 0177cec440
39 changed files with 110 additions and 110 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en/config/inbounds/hysteria.md
+4 -4
View File
@@ -1,7 +1,7 @@
# Hysteria
::: tip
The `hysteria protocol` itself has no authentication; `clients` only take effect when used with the `hysteria` transport layer.
The `hysteria protocol` itself has no authentication; `users` only take effect when used with the `hysteria` transport layer.
:::
## InboundConfigurationObject
@@ -9,7 +9,7 @@ The `hysteria protocol` itself has no authentication; `clients` only take effect
```json
{
"version": 2,
"clients": [
"users": [
{
"auth": "5783a3e7-e373-51cd-8642-c83782b807c5",
"level": 0,
@@ -23,11 +23,11 @@ The `hysteria protocol` itself has no authentication; `clients` only take effect
Hysteria version, must be 2.
> `clients`: \[ [ClientObject](#clientobject) \]
> `users`: \[ [UserObject](#userobject) \]
An array representing a group of users approved by the server.
### ClientObject
### UserObject
```json
{
docs/en/config/inbounds/shadowsocks.md
+2 -2
View File
@@ -37,7 +37,7 @@ Under the "none" encryption method, traffic will be transmitted in plain text. T
"password": "114514",
"level": 0,
"email": "love@xray.com",
"clients": [
"users": [
{
"password": "1919810",
"method": "aes-128-gcm"
@@ -88,7 +88,7 @@ The value of `level` corresponds to the `level` value in [policy](../policy.md#l
User email, used to distinguish traffic from different users (logs, statistics).
## ClientObject
## UserObject
```json
{
docs/en/config/inbounds/trojan.md
+5 -5
View File
@@ -10,7 +10,7 @@ Trojan is designed to work over correctly configured encrypted TLS tunnels.
```json
{
"clients": [
"users": [
{
"password": "password",
"email": "love@xray.com",
@@ -25,11 +25,11 @@ Trojan is designed to work over correctly configured encrypted TLS tunnels.
}
```
> `clients`: \[ [ClientObject](#clientobject) \]
> `users`: \[ [UserObject](#userobject) \]
An array representing a group of users accepted by the server.
Each item is a [ClientObject](#clientobject).
Each item is a [UserObject](#userobject).
> `fallbacks`: \[ [FallbackObject](../features/fallback.md) \]
@@ -41,7 +41,7 @@ Xray's Trojan has complete support for fallbacks, and the configuration method i
The conditions for triggering fallback are also similar to VLESS: the length of the first packet < 58, OR the 57th byte is not `\r` (because Trojan has no protocol version), OR authentication fails.
:::
### ClientObject
### UserObject
```json
{
@@ -60,7 +60,7 @@ Required, any string.
Email address, optional, used to identify the user.
::: danger
If there are multiple ClientObjects, please note that emails must not be duplicated.
If there are multiple UserObjects, please note that emails must not be duplicated.
:::
> `level`: number
docs/en/config/inbounds/vless.md
+4 -4
View File
@@ -8,7 +8,7 @@ Unlike [VMess](./vmess.md), VLESS does not depend on system time. The authentica
```json
{
"clients": [
"users": [
{
"id": "5783a3e7-e373-51cd-8642-c83782b807c5",
"level": 0,
@@ -26,11 +26,11 @@ Unlike [VMess](./vmess.md), VLESS does not depend on system time. The authentica
}
```
> `clients`: \[ [ClientObject](#clientobject) \]
> `users`: \[ [UserObject](#userobject) \]
An array representing a group of users approved by the server.
Each item is a user [ClientObject](#clientobject).
Each item is a user [UserObject](#userobject).
> `decryption`: "none"
@@ -58,7 +58,7 @@ The last block is identified by the core as the parameter used to authenticate t
An array containing a series of powerful fallback distribution configurations (optional).
For specific fallback configurations, please click [FallbackObject](../features/fallback.md#fallbacks-configuration).
### ClientObject
### UserObject
```json
{
docs/en/config/inbounds/vmess.md
+5 -5
View File
@@ -10,7 +10,7 @@ VMess depends on system time. Please ensure that the system UTC time of the devi
```json
{
"clients": [
"users": [
{
"id": "5783a3e7-e373-51cd-8642-c83782b807c5",
"level": 0,
@@ -23,19 +23,19 @@ VMess depends on system time. Please ensure that the system UTC time of the devi
}
```
> `clients`: \[ [ClientObject](#clientobject) \]
> `users`: \[ [UserObject](#userobject) \]
An array representing a group of users accepted by the server.
Each item is a [ClientObject](#clientobject).
Each item is a [UserObject](#userobject).
When this configuration is used for dynamic ports, Xray will automatically create users.
> `default`: [DefaultObject](#defaultobject)
Optional. Default configuration for clients. Only valid when used in conjunction with `detour`.
Optional. Default configuration for `users`. Only valid when used in conjunction with `detour`.
### ClientObject
### UserObject
```json
{
docs/en/config/reverse.md
+1 -1
View File
@@ -227,7 +227,7 @@ Inbounds:
"port": 1024,
"protocol": "vmess",
"settings": {
"clients": [
"users": [
{
"id": "5783a3e7-e373-51cd-8642-c83782b807c5"
}
docs/en/config/transports/hysteria.md
+1 -1
View File
@@ -37,7 +37,7 @@ Hysteria version, must be 2.
Hysteria authentication password. Must be consistent between the server and the client.
When used with `hysteria inbound`, it will be overridden by `clients` (if it exists).
When used with `hysteria inbound`, it will be overridden by `users` (if it exists).
> `udpIdleTimeout`: number
docs/en/document/config.md
+2 -2
View File
@@ -9,7 +9,7 @@ To configure more complex features, please refer to the detailed instructions in
::: danger
To avoid your traffic being decrypted,<br>
You should use `xray uuid` or `uuidgen` to generate a unique UUID.<br>
On the server side, put it in `inbounds[0].settings.clients[0].id`.<br>
On the server side, put it in `inbounds[0].settings.users[0].id`.<br>
On the client side, put it in `outbounds[0].settings.vnext[0].users[0].id`.<br>
:::
@@ -24,7 +24,7 @@ You need a server outside the firewall to run the server-side Xray. The configur
"port": 10086, // Server listening port
"protocol": "vmess",
"settings": {
"clients": [
"users": [
{
"id": "b831381d-6324-4d53-ad4f-8cda48b30811" // Remember to replace this field, generate using `xray uuid` or `uuidgen`
}
docs/en/document/level-0/ch07-xray-server.md
+1 -1
View File
@@ -190,7 +190,7 @@ First, various configurations can refer to the [official VLESS configuration exa
"port": 443,
"protocol": "vless",
"settings": {
"clients": [
"users": [
{
"id": "", // Fill in your UUID
"flow": "xtls-rprx-vision",
docs/en/document/level-1/fallbacks-lv1.md
+6 -6
View File
@@ -13,7 +13,7 @@ If you used the [Xray Configuration](../level-0/ch07-xray-server.md#_7-4-configu
"port": 443,
"protocol": "vless",
"settings": {
"clients": [
"users": [
// ... ...
],
"decryption": "none",
@@ -140,7 +140,7 @@ Now that you understand what the [Perfect Form of Fallback] is, you can get your
"port": 443,
"protocol": "vless",
"settings": {
"clients": [
"users": [
{
"id": "", // Fill in your UUID
"flow": "xtls-rprx-vision",
@@ -235,7 +235,7 @@ How do we explain this configuration in plain language?
"listen": "127.0.0.1",
"protocol": "trojan",
"settings": {
"clients": [
"users": [
{
"password": "", // Fill in your password
"level": 0,
@@ -270,7 +270,7 @@ How do we explain this configuration in plain language?
"listen": "127.0.0.1",
"protocol": "vless",
"settings": {
"clients": [
"users": [
{
"id": "", // Fill in your UUID
"level": 0,
@@ -298,7 +298,7 @@ How do we explain this configuration in plain language?
"listen": "127.0.0.1",
"protocol": "vmess",
"settings": {
"clients": [
"users": [
{
"id": "", // Fill in your UUID
"level": 0,
@@ -336,7 +336,7 @@ How do we explain this configuration in plain language?
"listen": "127.0.0.1",
"protocol": "vmess",
"settings": {
"clients": [
"users": [
{
"id": "", // Fill in your UUID
"level": 0,
docs/en/document/level-1/fallbacks-with-sni.md
+2 -2
View File
@@ -80,7 +80,7 @@ acme.sh --install-cert -d example.com --fullchain-file /etc/ssl/xray/cert.pem --
"port": 443,
"protocol": "vless",
"settings": {
"clients": [
"users": [
{
"id": "UUID",
"flow": "xtls-rprx-vision"
@@ -135,7 +135,7 @@ acme.sh --install-cert -d example.com --fullchain-file /etc/ssl/xray/cert.pem --
"port": 5000,
"protocol": "vmess",
"settings": {
"clients": [
"users": [
{
"id": "UUID"
}
docs/en/document/level-2/nginx_or_haproxy_tls_tunnel.md
+1 -1
View File
@@ -111,7 +111,7 @@ Enable auto-start on boot:
"listen": "/dev/shm/vless.sock,0666",
"protocol": "vless",
"settings": {
"clients": [
"users": [
{
"id": "uuid"
}
docs/en/document/level-2/tproxy_ipv4_and_ipv6.md
+2 -2
View File
@@ -76,7 +76,7 @@ If the Xray program is not installed on the side router, you can manually downlo
"port": 443,
"users": [
{
"id": "uuid", // Fill in UUID. Can be generated by typing 'xray uuid' in terminal; Arbitrary strings are also supported (https://xtls.github.io/en/config/inbounds/vless.html#clientobject)
"id": "uuid", // Fill in UUID. Can be generated by typing 'xray uuid' in terminal; Arbitrary strings are also supported (https://xtls.github.io/en/config/inbounds/vless.html#userobject)
"encryption": "none",
"flow": "xtls-rprx-vision"
}
@@ -222,7 +222,7 @@ If the Xray program is not installed on the side router, you can manually downlo
"port": 443,
"protocol": "vless",
"settings": {
"clients": [
"users": [
{
"id": "uuid", // Same as client
"flow": "xtls-rprx-vision"