> For the complete documentation index, see [llms.txt](https://loyalproxy.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://loyalproxy.gitbook.io/docs/proxy-configuration/proxy-tool-setup-tutorial/clash.md).

# Clash

{% hint style="warning" %}
**Usage Notice:** All LoyalProxy proxy products must be operated in an overseas network environment. Please ensure that you have already configured the corresponding overseas network environment yourself.
{% endhint %}

This article provides a detailed introduction on how to use the **Clash Verge client** to deploy **Static Residential IPs** through chained proxying, achieving a more stable and secure network access environment.

> **Tip**: The usage method for dynamic residential IPs is the same as that for static residential IPs.

### 1. Preparations

**Download the Software**

Download the Clash Verge client version corresponding to your operating system and complete the installation. **Demo system: Windows 10**

**Prepare Materials**

* You need to prepare a usable overseas network environment yourself.
* **Static Residential IP information**: Obtain the following information from [LoyalProxy](https://www.LoyalProxy.com/zh-cn/):
  * Server address
  * Port number
  * Username
  * Password

### 2. Add an Overseas Subscription

1. Open Clash Verge and click **Subscription** in the left menu bar.
2. Click **Add Subscription**, paste your overseas subscription link into the input field, and save.
3. After updating the subscription, go to **Settings** → **Profile Management**, locate the `config-verge.yaml` file in the local folder, and open it with a text editor for editing. **It is recommended to make a backup copy before editing.**

<figure><img src="https://779989668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwsS3NgJFgFQvWFmv0zaY%2Fuploads%2FkjKxhh1AjU1GMZ5gw6B7%2Fimage.png?alt=media&#x26;token=5246326b-d288-413a-a1ca-1caaf566c9a0" alt=""><figcaption></figcaption></figure>

<figure><img src="https://779989668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwsS3NgJFgFQvWFmv0zaY%2Fuploads%2FX7dAsKEqWKDC58l9WX8R%2Fimage.png?alt=media&#x26;token=79c27564-5ff0-4797-bd7d-32a1d27a847b" alt=""><figcaption></figcaption></figure>

In the configuration file, you can see node information similar to the following:

```yaml
proxies:
  - name: "Node Name"
    server: "Server Address"
    port: Port Number
    type: Protocol Type
    cipher: Encryption Algorithm
    password: "Password"
```

The nodes in the configuration file contain the following required parameters:

* **name**: Node display name
* **server**: Server address (IP or domain name)
* **port**: Connection port
* **type**: Protocol type (such as `trojan`, `vmess`, `shadowsocks`)
* **cipher**: Encryption algorithm
* **password**: Authentication password

### 3. Modify the Configuration File

Add the following two types of nodes to the `proxies:` section of the configuration file to implement a chained proxy structure:

```yaml
proxies:
  # Type A: Entry node (overseas node)
  - name: Entry Node
    type: Protocol Type
    server: Server Address
    port: Port Number
    cipher: Encryption Algorithm
    password: Password
    udp: true

  # Type B: Chained exit (static residential IP)
  - name: Static Proxy
    type: http
    server: Static IP Address
    port: Port Number
    username: Username
    password: Password
    udp: true
    dialer-proxy: Entry Node

proxy-groups:
  - name: Chained Proxy
    type: select
    proxies:
      - Entry Node
      - Static Proxy
```

**Filling Instructions**:

* **Entry Node**: Replace with your overseas stable node information that supports UDP.
* **Static Proxy**: Replace with the static residential IP information obtained from [LoyalProxy](https://www.LoyalProxy.com/zh-cn/).
* **dialer-proxy: "Entry Node"**: Indicates that this static proxy will connect through the "Entry Node", forming a chained proxy.

### 4. Import the Configuration

**Import the Configuration File**

Save the modified configuration file as `config.yaml` and import it in the following ways:

**Method 1: Drag-and-drop Import**

Directly drag the `config.yaml` file into the Clash Verge main interface.

**Method 2: Manual Import**

1. Click **Proxy** on the left.
2. Click the **New** button.
3. Select the type as **Local**.
4. Click **Select File**, locate and select your `config.yaml` file. **The file name can be customized.**

<figure><img src="https://779989668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwsS3NgJFgFQvWFmv0zaY%2Fuploads%2F3nfAoZTTrKUhaq4GMkJ8%2Fimage.png?alt=media&#x26;token=6f4715a3-ec47-4e46-835d-26c06e4fba40" alt=""><figcaption></figcaption></figure>

### 5. Testing and Usage

**Enable the Configuration File**

1. Click **Subscription** on the left.
2. Find the configuration file you just added in the list.
3. Click **Start** on the file.

<figure><img src="https://779989668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwsS3NgJFgFQvWFmv0zaY%2Fuploads%2F9cJ2bqagIe8iFGU4bOrI%2Fimage.png?alt=media&#x26;token=4a65e3a9-1d7c-449a-a7cc-6e1861ac7918" alt=""><figcaption></figcaption></figure>

**Test Proxy Connectivity**

1. Switch to the **Proxy** page.
2. Find **Chained Proxy** in the list.
3. Check whether a latency value is displayed on the right (display indicates a successful connection).

<figure><img src="https://779989668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwsS3NgJFgFQvWFmv0zaY%2Fuploads%2FRk0hd76dcIcUZ5bERyCe%2Fimage.png?alt=media&#x26;token=2a23110a-d098-4726-84e0-6aeab8ad985c" alt=""><figcaption></figcaption></figure>

**Select Proxy Mode**

At the top of the Clash Verge main interface, you can choose between the following two modes:

* **Rule Mode**: Intelligent traffic splitting based on preset rules.
* **Global Mode**: All traffic is forwarded through the proxy.

***

> At this point, you have successfully configured a chained proxy based on Clash Verge and can securely and stably access target websites through static residential IPs.
