github
/
Xray-docs-next
mirror of https://github.com/XTLS/Xray-docs-next
1
0
Fork 0
Code Issues Releases Wiki Activity

Prettified Code!

pull/730/head
dependabot[bot] 2025-08-04 19:24:01 +00:00 committed by GitHub Action
parent eadea5efb3
commit c8684a90af
4 changed files with 20 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/config/README.md
View File

@ -12,7 +12,7 @@ Xray 的配置文件为 json 格式, 客户端和服务端的配置格式没有
```json ```json
{ {
"vsersion":{}, "vsersion": {},
"log": {}, "log": {},
"api": {}, "api": {},
"dns": {}, "dns": {},

19
docs/en/document/level-0/ch07-xray-server.md
View File

@ -123,7 +123,6 @@ chmod +r ~/xray_cert/xray.key
In addition, when recording animated images, the script did not include a command to restart `Xray` because `Xray` plans to support the [Certificate Hot Update] function, which means that `Xray` will automatically identify certificate updates and reload certificates without manual restart. After the function is added, I will modify `config.json` appropriately In addition, when recording animated images, the script did not include a command to restart `Xray` because `Xray` plans to support the [Certificate Hot Update] function, which means that `Xray` will automatically identify certificate updates and reload certificates without manual restart. After the function is added, I will modify `config.json` appropriately
to enable this setting and delete the restart command in the script. to enable this setting and delete the restart command in the script.
::: :::
4. Add [executable] permissions to this file 4. Add [executable] permissions to this file
``` ```
@ -179,7 +178,6 @@ First, you can refer to the [official VLESS configuration example](https://githu
::: warning ::: warning
This location is not the standard log file location of `Xray`. It is placed here to avoid permission issues that cause trouble for new users. Once you are familiar with it, it is recommended to return to the default location: `/var/log/xray/access.log` and `/var/log/xray/error.log`. This location is not the standard log file location of `Xray`. It is placed here to avoid permission issues that cause trouble for new users. Once you are familiar with it, it is recommended to return to the default location: `/var/log/xray/access.log` and `/var/log/xray/error.log`.
::: :::
4. Because Xray is used by the nobody user by default, we need to allow other users to have "write" permissions (`*.log` means all files with the suffix `log`, and the efficiency advantage of the `CLI` interface gradually appears at this time) 4. Because Xray is used by the nobody user by default, we need to allow other users to have "write" permissions (`*.log` means all files with the suffix `log`, and the efficiency advantage of the `CLI` interface gradually appears at this time)
```shell ```shell
@ -424,15 +422,16 @@ deb http://deb.debian.org/debian buster-backports main
9. Refresh the software library and query the latest version of the official Debian kernel and install it. Please be sure to install the version corresponding to your VPS (this article takes the more common [amd64] as an example). 9. Refresh the software library and query the latest version of the official Debian kernel and install it. Please be sure to install the version corresponding to your VPS (this article takes the more common [amd64] as an example).
```shell ```shell
sudo apt update && sudo apt -t buster-backports install linux-image-amd64 sudo apt update && sudo apt -t buster-backports install linux-image-amd64
``` ```
::: warning Note ::: warning Note
If your VPS supports it, you can try the [cloud server dedicated kernel] `linux-image-cloud-amd64`. The advantages are simplicity and low resource usage. The disadvantage is that some students have reported that forced installation on an unsupported system will cause the system to fail to boot (the kernel cannot be recognized). If your VPS supports it, you can try the [cloud server dedicated kernel] `linux-image-cloud-amd64`. The advantages are simplicity and low resource usage. The disadvantage is that some students have reported that forced installation on an unsupported system will cause the system to fail to boot (the kernel cannot be recognized).
To avoid the tragedy of being unable to identify, please make sure: To avoid the tragedy of being unable to identify, please make sure:
- Take a system snapshot before trying, or - Take a system snapshot before trying, or
- You have `vnc` to save the day (and you know how to use it) - You have `vnc` to save the day (and you know how to use it)
@ -459,9 +458,9 @@ net.ipv4.tcp_congestion_control=bbr
12. Restart the VPS to make the kernel update and `BBR` settings take effect 12. Restart the VPS to make the kernel update and `BBR` settings take effect
```shell ```shell
sudo reboot sudo reboot
``` ```
13. The complete process is demonstrated as follows: 13. The complete process is demonstrated as follows:
@ -476,21 +475,25 @@ If you are not sure whether your VPS supports it, please follow the command in s
14. Confirm that `BBR` is enabled 14. Confirm that `BBR` is enabled
If you want to confirm whether `BBR` is enabled correctly, you can use the following command: If you want to confirm whether `BBR` is enabled correctly, you can use the following command:
```shell ```shell
lsmod | grep bbr lsmod | grep bbr
``` ```
This should return the following result: This should return the following result:
``` ```
tcp_bbr tcp_bbr
``` ```
If you want to confirm whether the `fq` algorithm is enabled correctly, you can use the following command: If you want to confirm whether the `fq` algorithm is enabled correctly, you can use the following command:
```shell ```shell
lsmod | grep fq lsmod | grep fq
``` ```
This should return the following result: This should return the following result:
``` ```
sch_fq sch_fq
``` ```