Remove invalid VuePress code from docs

Meo597 · Meo597 · commit aefcd935e12e · 2026-01-24T06:33:55.000+08:00
diff --git a/docs/about/news.md b/docs/about/news.md
@@ -1,7 +1,3 @@
----
-sidebar: auto
----
-
 # 大史记
 
 ## 2024.10.31 <badge>[24.10.31](https://github.com/XTLS/Xray-core/releases/tag/v24.10.31)</badge>
diff --git a/docs/config/index.md b/docs/config/index.md
@@ -1,7 +1,4 @@
----
-title: 配置文件
-lang: zh-CN
----
+# 配置文件
 
 > **这个章节将告诉您所有的 Xray 配置细节，掌握这些内容，在您手中 Xray 将发挥更大威力。**
 
diff --git a/docs/document/install.md b/docs/document/install.md
@@ -163,6 +163,6 @@ ghcr.io/xtls/xray-core 版本映像：
   - [GoXRay](https://github.com/goxray/desktop)
   - [AnyPortal](https://github.com/AnyPortal/AnyPortal)
 
-# UUID 生成器
+## UUID 生成器
 
 第三方的 UUID 生成器 [uuidgenerator.net](https://www.uuidgenerator.net)
diff --git a/docs/document/level-1/fallbacks-with-sni.md b/docs/document/level-1/fallbacks-with-sni.md
@@ -1,7 +1,3 @@
----
-title: SNI 回落
----
-
 # 通过 SNI 回落功能实现伪装与按域名分流
 
 VLESS 是一种很轻的协议，和 Trojan 一样，不对流量进行复杂的加密和混淆，而是大隐隐于市，通过 TLS 协议加密，混杂在其他 HTTPS 流量中，在墙内外穿进穿出。为了更好的伪装以应对主动探测，Fallbacks 回落功能随 VLESS 同时出现。这篇教程将演示如何使用 Xray 中 VLESS 入站协议的回落功能配合 Nginx 或 Caddy 在保证伪装完全的前提下实现按域名分流。
diff --git a/docs/document/level-2/iptables_gid.md b/docs/document/level-2/iptables_gid.md
@@ -1,7 +1,3 @@
----
-title: GID 透明代理
----
-
 # 透明代理通过 gid 规避 Xray 流量
 
 在现有的 iptables 透明代理白话文(**[新 V2Ray 白话文指南-透明代理](https://guide.v2fly.org/app/transparent_proxy.html)** 、 **[新 V2Ray 白话文指南-透明代理(TPROXY)](https://guide.v2fly.org/app/tproxy.html)** 、 **[透明代理（TProxy）配置教程](./tproxy)**)教程中，对 Xray 流量的规避处理是打 mark 实现的。即对 Xray 出站流量打 mark，通过设置 iptables 规则对对应 mark 的流量直连，来规避 Xray 流量，防止回环。
diff --git a/docs/document/level-2/nginx_or_haproxy_tls_tunnel.md b/docs/document/level-2/nginx_or_haproxy_tls_tunnel.md
@@ -1,10 +1,8 @@
----
-title: Nginx 或 Haproxy 搭建 TLS 隧道隐藏指纹
----
+# Nginx 或 Haproxy 搭建 TLS 隧道隐藏指纹
 
 Nginx 或 Haproxy 实现的 HTTPS 隧道、HTTP/2 over HTTPS 隧道、WebSocket over HTTP/2 over HTTPS 隧道、gRPC over HTTP/2 over HTTPS 隧道以及自签证书双端认证的 gRPC over HTTP/2 over HTTPS 隧道
 
-# 客户端服务端 Nginx 构建 HTTPS 隧道隐藏指纹
+## 客户端服务端 Nginx 构建 HTTPS 隧道隐藏指纹
 
 网路结构：
 
diff --git a/docs/document/level-2/redirect.md b/docs/document/level-2/redirect.md
@@ -1,7 +1,3 @@
----
-title: 出站流量重定向
----
-
 # 基于 fwmark 或 sendThrough 的流量重定向
 
 通过 Xray 将特定的流量指向特定出口，实现全局路由“分流”
diff --git a/docs/document/level-2/tproxy.md b/docs/document/level-2/tproxy.md
@@ -1,7 +1,3 @@
----
-title: TProxy 透明代理
----
-
 # 透明代理（TProxy）配置教程
 
 本配置基于[TProxy 透明代理的新 V2Ray 白话文教程](https://guide.v2fly.org/app/tproxy.html)，加入了 Xray 的新特性，使用 VLESS + XTLS Vision 方案，并将旧教程中默认出站代理的分流方式改为默认出站直连，使用者请按照实际情况进行修改。
diff --git a/docs/document/level-2/tproxy_ipv4_and_ipv6.md b/docs/document/level-2/tproxy_ipv4_and_ipv6.md
@@ -1,7 +1,3 @@
----
-title: TProxy 透明代理 (ipv4 and ipv6)
----
-
 # TProxy 透明代理（ipv4 and ipv6）配置教程
 
 本配置参考了[TProxy 透明代理的新 V2Ray 白话文教程](https://guide.v2fly.org/app/tproxy.html)，[透明代理（TProxy）配置教程](https://xtls.github.io/document/level-2/tproxy.html#%E5%BC%80%E5%A7%8B%E4%B9%8B%E5%89%8D)以及[透明代理通过 gid 规避 Xray 流量](https://xtls.github.io/document/level-2/iptables_gid.html)，加入了透明代理对 ipv6 的支持，并且使用 VLESS-TCP-XTLS-RPRX-Vision 方案对抗封锁 (推荐使用 1.7.2 及之后版本)。
diff --git a/docs/document/level-2/traffic_stats.md b/docs/document/level-2/traffic_stats.md
@@ -1,7 +1,3 @@
----
-title: 流量统计
----
-
 # 流量统计配置教程
 
 请熟悉[流量统计 白话文教程](https://guide.v2fly.org/advanced/traffic.html)，本文在其基础上适配了 Xray（1.5.9+）。
diff --git a/docs/document/level-2/warp.md b/docs/document/level-2/warp.md
@@ -1,7 +1,3 @@
----
-title: 通过 Cloudflare Warp 增强代理安全性
----
-
 # 通过 Cloudflare Warp 增强代理安全性
 
 Xray（1.6.5+）新加入了 WireGuard 出站，虽然增加的代码和依赖会增大 core 体积，但是我们认为这是一个很有必要的新功能，原因有三：
diff --git a/docs/en/about/news.md b/docs/en/about/news.md
@@ -1,7 +1,3 @@
----
-sidebar: auto
----
-
 # Grand Chronicle
 
 ## 2024.10.31 <badge>[24.10.31](https://github.com/XTLS/Xray-core/releases/tag/v24.10.31)</badge>
@@ -484,7 +480,7 @@ Now bringing a sneak peek of X-flutter, look forward to what it will look like~
 
 ## 2021.3.25
 
-Yes, still changing. -_-
+Yes, still changing. -\_-
 
 ## 2021.3.15
 
@@ -530,7 +526,7 @@ The documentation site is quietly undergoing some mysterious changes... 🙊🙊
 
 - Support for SS protocol has become stronger **again**, supporting single-port multi-user!
 - Support for Trojan protocol has also become stronger **again**; Trojan fallback also unlocked a new posture for SNI routing~!
-- _(VLESS: _cries_)_
+- _(VLESS: \_cries_)\_
 - Weird UDP BUGs have been eliminated. One word: "Stable".
 - Sniffing can exclude domains you don't want to sniff, enabling some new ways to play.
 - Salute to [@Bohan Yang](https://github.com/bohanyang) who discovers issues -> opens issues -> self-tests -> self-analyzes -> finds the problem -> solves it -> and then submits PRs to upstream and downstream!
diff --git a/docs/en/config/index.md b/docs/en/config/index.md
@@ -1,7 +1,4 @@
----
-title: Configuration File
-lang: en-US
----
+# Configuration File
 
 > **This chapter will tell you all the details of Xray configuration. Mastering this content will allow you to unleash the greater power of Xray.**
 
diff --git a/docs/en/document/install.md b/docs/en/document/install.md
@@ -160,6 +160,6 @@ ghcr.io/xtls/xray-core version image:
   - [GoXRay](https://github.com/goxray/desktop)
   - [AnyPortal](https://github.com/AnyPortal/AnyPortal)
 
-# UUID Generator
+## UUID Generator
 
 Third-party UUID generator: [uuidgenerator.net](https://www.uuidgenerator.net)
diff --git a/docs/en/document/level-1/fallbacks-with-sni.md b/docs/en/document/level-1/fallbacks-with-sni.md
@@ -1,7 +1,3 @@
----
-title: SNI Fallback
----
-
 # Camouflage and Routing by Domain via SNI Fallback
 
 VLESS is a lightweight protocol. Like Trojan, it does not perform complex encryption and obfuscation on traffic. Instead, it "hides in plain sight" by using the TLS protocol for encryption, blending in with other HTTPS traffic to pass in and out of the firewall. To better camouflage against active probing, the **Fallbacks** feature was introduced alongside VLESS. This tutorial will demonstrate how to use the fallback function of the VLESS inbound protocol in Xray, combined with Nginx or Caddy, to achieve routing based on domain names while ensuring complete camouflage.
diff --git a/docs/en/document/level-2/iptables_gid.md b/docs/en/document/level-2/iptables_gid.md
@@ -1,7 +1,3 @@
----
-title: GID Transparent Proxy
----
-
 # Transparent Proxy: Bypassing Xray Traffic via GID
 
 In existing `iptables` transparent proxy guides (**[New V2Ray Plain English Guide - Transparent Proxy](https://guide.v2fly.org/app/transparent_proxy.html)**, **[New V2Ray Plain English Guide - Transparent Proxy (TPROXY)](https://guide.v2fly.org/app/tproxy.html)**, **[Transparent Proxy (TProxy) Configuration Tutorial](./tproxy)**), the method used to bypass Xray traffic (to prevent routing loops) involves marking packets (`mark`). Specifically, marks are applied to Xray's outbound traffic, and `iptables` rules are set to direct traffic with corresponding marks to go out directly, thus bypassing the Xray proxy process.
@@ -145,11 +141,11 @@ ulimit -SHn 1000000
 sudo -u xray_tproxy xray -c /etc/xray/config.json &
 ```
 
-*First command:*
+_First command:_
 
 Changes the maximum number of open files. It is only effective for the current terminal and must be run every time before starting Xray. This command sets the maximum file limit for the client.
 
-*Second command:*
+_Second command:_
 
 Runs the Xray client as a user with `uid=0` and a non-zero `gid`. The `&` at the end indicates running in the background.
 
diff --git a/docs/en/document/level-2/nginx_or_haproxy_tls_tunnel.md b/docs/en/document/level-2/nginx_or_haproxy_tls_tunnel.md
@@ -1,10 +1,8 @@
----
-title: Using Nginx or HAProxy to Build TLS Tunnels to Hide Fingerprints
----
+# Using Nginx or HAProxy to Build TLS Tunnels to Hide Fingerprints
 
 HTTPS tunnels, HTTP/2 over HTTPS tunnels, WebSocket over HTTP/2 over HTTPS tunnels, gRPC over HTTP/2 over HTTPS tunnels implemented via Nginx or HAProxy, and gRPC over HTTP/2 over HTTPS tunnels with self-signed certificate mutual authentication.
 
-# Building HTTPS Tunnels with Nginx on Client & Server to Hide Fingerprints
+## Building HTTPS Tunnels with Nginx on Client & Server to Hide Fingerprints
 
 Network Structure:
 
diff --git a/docs/en/document/level-2/redirect.md b/docs/en/document/level-2/redirect.md
@@ -1,7 +1,3 @@
----
-title: Outbound Traffic Redirection
----
-
 # Traffic Redirection Based on fwmark or sendThrough
 
 Direct specific traffic to specific exits via Xray to achieve global routing "traffic splitting".
diff --git a/docs/en/document/level-2/tproxy.md b/docs/en/document/level-2/tproxy.md
@@ -1,7 +1,3 @@
----
-title: TProxy Transparent Proxy
----
-
 # Transparent Proxy (TProxy) Configuration Tutorial
 
 This configuration is based on the [New V2Ray Plain Guide for Transparent Proxy (TProxy)](https://guide.v2fly.org/app/tproxy.html), adding new features from Xray. It utilizes the VLESS + XTLS Vision scheme. Unlike the old tutorial which defaulted to proxying outbound traffic, this configuration defaults to direct connection for outbound traffic. Users should adjust this according to their actual needs.
@@ -14,7 +10,7 @@ Please check that your device has an active network connection, the server-side
 
 It is worth noting that many transparent proxy tutorials instruct you to enable IP Forwarding on Linux. However, doing so can degrade `Splice` performance. For details, please refer to [Detective Story Part 3: How we solved the mystery of Splice performance dropping even below Direct](https://github.com/XTLS/Xray-core/discussions/59).
 
-I would like to add that many transparent proxy tutorials use Netfilter for traffic splitting (routing), allowing direct traffic to go out without passing through Xray. In that case, IP Forwarding must be enabled. However, some tutorials, like this one, direct *all* traffic into Xray, and the routing module within Xray handles the splitting. In this scenario, IP Forwarding does **not** need to be enabled.
+I would like to add that many transparent proxy tutorials use Netfilter for traffic splitting (routing), allowing direct traffic to go out without passing through Xray. In that case, IP Forwarding must be enabled. However, some tutorials, like this one, direct _all_ traffic into Xray, and the routing module within Xray handles the splitting. In this scenario, IP Forwarding does **not** need to be enabled.
 
 ## Xray Configuration
 
diff --git a/docs/en/document/level-2/tproxy_ipv4_and_ipv6.md b/docs/en/document/level-2/tproxy_ipv4_and_ipv6.md
@@ -1,7 +1,3 @@
----
-title: TProxy Transparent Proxy (IPv4 and IPv6)
----
-
 # TProxy Transparent Proxy (IPv4 and IPv6) Configuration Tutorial
 
 This configuration is based on the [New V2Ray Plain English Guide for TProxy Transparent Proxy](https://guide.v2fly.org/app/tproxy.html), the [Transparent Proxy (TProxy) Configuration Tutorial](https://xtls.github.io/document/level-2/tproxy.html#%E5%BC%80%E5%A7%8B%E4%B9%8B%E5%89%8D), and [Bypassing Xray Traffic via GID](https://xtls.github.io/document/level-2/iptables_gid.html). It adds support for IPv6 transparent proxying and utilizes the VLESS-TCP-XTLS-RPRX-Vision scheme to counter blocking (version 1.7.2 or later is recommended).
diff --git a/docs/en/document/level-2/traffic_stats.md b/docs/en/document/level-2/traffic_stats.md
@@ -1,7 +1,3 @@
----
-title: Traffic Statistics
----
-
 # Traffic Statistics Configuration Tutorial
 
 Please familiarize yourself with the [Traffic Statistics Plain Language Guide](https://guide.v2fly.org/advanced/traffic.html). This article adapts those concepts for Xray (1.5.9+).
diff --git a/docs/en/document/level-2/warp.md b/docs/en/document/level-2/warp.md
@@ -1,15 +1,11 @@
----
-title: Enhancing Proxy Security via Cloudflare Warp
----
-
 # Enhancing Proxy Security via Cloudflare Warp
 
 Xray (1.6.5+) has added a WireGuard outbound. Although the additional code and dependencies increase the core size, we believe this is a highly necessary new feature for three reasons:
 
 1. Through recent discussions and [experiments](https://github.com/net4people/bbs/issues/129#issuecomment-1308102504), we know that routing traffic back to China via a proxy is insecure. One countermeasure is to route return traffic to a blackhole. The downside is that if `geosite` and `geoip` rules are not updated in time, or if beginners don't know how to configure routing properly on the client side, legitimate traffic enters the blackhole, affecting the user experience.
-    By routing return traffic (traffic destined for China) to Cloudflare Warp instead, we can achieve the same level of security without impacting the user experience.
+   By routing return traffic (traffic destined for China) to Cloudflare Warp instead, we can achieve the same level of security without impacting the user experience.
 2. It is well known that most proxy providers ("Airports") log user domain access history, and some even audit and block certain user traffic. One way to protect user privacy is to use a chain proxy on the client side.
-    The WireGuard lightweight VPN protocol used by Warp adds a layer of encryption within the proxy layer. For the proxy provider, the destination of all user traffic appears to be Warp, thereby maximizing privacy protection.
+   The WireGuard lightweight VPN protocol used by Warp adds a layer of encryption within the proxy layer. For the proxy provider, the destination of all user traffic appears to be Warp, thereby maximizing privacy protection.
 3. Ease of use. A single core can handle routing, WireGuard Tun, and chain proxy settings.
 
 ## Applying for a Warp Account
diff --git a/docs/ru/about/news.md b/docs/ru/about/news.md
@@ -1,7 +1,3 @@
----
-sidebar: auto
----
-
 # 大史记
 
 ## 2024.10.31 <badge>[24.10.31](https://github.com/XTLS/Xray-core/releases/tag/v24.10.31)</badge>
diff --git a/docs/ru/config/index.md b/docs/ru/config/index.md
@@ -1,7 +1,4 @@
----
-title: Конфигурационный файл
-lang: ru-RU
----
+# Конфигурационный файл
 
 > **В этом разделе вы узнаете все детали настройки Xray. Овладев этими знаниями, вы сможете раскрыть весь потенциал Xray.**
 
diff --git a/docs/ru/document/index.md b/docs/ru/document/index.md
@@ -1,7 +1,3 @@
----
-sidebar: auto
----
-
 # Быстрый старт
 
 > **В этой главе вы узнаете, как максимально просто получить Xray и начать его использовать.**
diff --git a/docs/ru/document/install.md b/docs/ru/document/install.md
@@ -156,6 +156,6 @@ Xray предлагает два способа проверки:
   - [GoXRay](https://github.com/goxray/desktop)
   - [AnyPortal](https://github.com/AnyPortal/AnyPortal)
 
-# Генератор UUID
+## Генератор UUID
 
 Генератор UUID от сторонних разработчиков: [uuidgenerator.net](https://www.uuidgenerator.net)
diff --git a/docs/ru/document/level-1/fallbacks-with-sni.md b/docs/ru/document/level-1/fallbacks-with-sni.md
@@ -1,7 +1,3 @@
----
-title: SNI Fallback
----
-
 # Маскировка и разделение трафика по доменам с помощью функции SNI Fallback
 
 VLESS - это очень легкий протокол, который, как и Trojan, не использует сложного шифрования и обфускации трафика. Вместо этого он, подобно тому, как искусный мастер кунг-фу скрывает свою силу, шифрует трафик с помощью протокола TLS, маскируя его под обычный HTTPS-трафик и позволяя ему беспрепятственно проходить через Великий китайский файрвол. Для лучшей маскировки от активного зондирования вместе с VLESS была представлена функция Fallbacks (резервирование). В этой статье мы рассмотрим, как использовать функцию Fallbacks входящего протокола VLESS в Xray совместно с Nginx или Caddy для реализации разделения трафика по доменам при обеспечении полной маскировки.
diff --git a/docs/ru/document/level-2/iptables_gid.md b/docs/ru/document/level-2/iptables_gid.md
@@ -1,7 +1,3 @@
----
-title: GID Прозрачное проксирование
----
-
 # Прозрачное проксирование: Исключение трафика Xray с помощью GID
 
 В существующих русскоязычных руководствах по прозрачному проксированию с использованием iptables (**[Новое руководство по V2Ray на русском языке - Прозрачное проксирование](https://guide.v2fly.org/app/transparent_proxy.html)**, **[Новое руководство по V2Ray на русском языке - Прозрачное проксирование (TPROXY)](https://guide.v2fly.org/app/tproxy.html)**, **[Руководство по настройке прозрачного проксирования (TProxy)](./tproxy)**) исключение трафика Xray осуществляется с помощью меток. Исходящий трафик Xray помечается, а затем с помощью правил iptables трафик с соответствующей меткой направляется напрямую, минуя Xray и предотвращая зацикливание.
diff --git a/docs/ru/document/level-2/nginx_or_haproxy_tls_tunnel.md b/docs/ru/document/level-2/nginx_or_haproxy_tls_tunnel.md
@@ -1,10 +1,8 @@
----
-title: Создание TLS-туннеля с помощью Nginx или Haproxy для скрытия отпечатков
----
+# Создание TLS-туннеля с помощью Nginx или Haproxy для скрытия отпечатков
 
 Nginx или Haproxy реализуют HTTPS-туннели, туннели HTTP/2 over HTTPS, туннели WebSocket over HTTP/2 over HTTPS, туннели gRPC over HTTP/2 over HTTPS, а также туннели gRPC over HTTP/2 over HTTPS с двусторонней аутентификацией по самозаверяющему сертификату.
 
-# Создание HTTPS-туннеля с помощью Nginx на стороне клиента и сервера для скрытия отпечатков
+## Создание HTTPS-туннеля с помощью Nginx на стороне клиента и сервера для скрытия отпечатков
 
 Сетевая структура:
 
diff --git a/docs/ru/document/level-2/redirect.md b/docs/ru/document/level-2/redirect.md
@@ -1,7 +1,3 @@
----
-title: Перенаправление исходящего трафика
----
-
 # Перенаправление трафика на основе fwmark или sendThrough
 
 Направление определенного трафика через определенный выходной узел с помощью Xray для реализации "разделения" глобальной маршрутизации
diff --git a/docs/ru/document/level-2/tproxy.md b/docs/ru/document/level-2/tproxy.md
diff --git a/docs/ru/document/level-2/tproxy_ipv4_and_ipv6.md b/docs/ru/document/level-2/tproxy_ipv4_and_ipv6.md
diff --git a/docs/ru/document/level-2/traffic_stats.md b/docs/ru/document/level-2/traffic_stats.md
diff --git a/docs/ru/document/level-2/warp.md b/docs/ru/document/level-2/warp.md
