> For the complete documentation index, see [llms.txt](https://jollyproxy.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://jollyproxy.gitbook.io/docs/proxy-configuration/proxy-tool-configuration-guide/clash.md).

# Clash

{% hint style="danger" icon="exclamation" %}
**Usage Notice:** All JollyProxy proxy products must be used in an overseas network environment. Please ensure that you have configured the corresponding overseas network environment yourself.
{% endhint %}

This article will provide a detailed guide on how to deploy a **Static Residential Proxy** using the **Clash Verge client** through chained proxying, achieving a more stable and secure network access environment.

> **Tip**: Residential proxies are used in the same way as static residential proxies.

### 1. Preparation

**Download the Software**

Download the appropriate version of the Clash Verge client for your operating system and complete the installation. **Demo system: Windows 10**

**Prepare the Materials**

* You need to prepare a working overseas network environment yourself.
* **Static Residential IP Information**: Obtain the following information from [JollyProxy](https://www.jollyproxy.com/):
  * Server address
  * Port number
  * Username
  * Password

### 2. Add an Overseas Subscription

1. Open Clash Verge and click **Subscription** in the left sidebar.
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 your 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 egress (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 stable overseas node information that supports UDP.
* **Static Proxy**: Replace with the static residential IP information obtained from [JollyProxy](https://www.jollyproxy.com/).
* **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 using one of the following methods:

**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. Test and Use

**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 (displayed means the connection is successful).

<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 the Proxy Mode**

At the top of the Clash Verge main interface, you can select one of the following two modes:

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

> You have now successfully configured a chained proxy based on Clash Verge and can securely and stably access target websites through the static residential proxy.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://jollyproxy.gitbook.io/docs/proxy-configuration/proxy-tool-configuration-guide/clash.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
