Hysteria
TIP
The hysteria protocol itself has no authentication; users only take effect when used with the hysteria transport layer.
InboundConfigurationObject
InboundConfigurationObject corresponds to the settings item in InboundObject.
json
{
"inbounds": [
{
// ...
"protocol": "hysteria",
"settings": {
"version": 2,
"users": [
{
"auth": "5783a3e7-e373-51cd-8642-c83782b807c5",
"level": 0,
"email": "love@xray.com"
}
]
}
}
]
}1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
version: number
Hysteria version, must be 2.
users: [ UserObject ]
An array representing a group of users approved by the server.
UserObject
json
{
"auth": "5783a3e7-e373-51cd-8642-c83782b807c5",
"level": 0,
"email": "love@xray.com"
}1
2
3
4
5
2
3
4
5
auth: string
A string of any length.
level: number
User level. The connection will use the local policy corresponding to this user level.
The value of level corresponds to the level value in policy. If not specified, the default is 0.
User email, used to distinguish traffic from different users (reflected in logs and statistics).
