> 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/v2rayn.md).

# v2rayN

{% 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 guide you through configuring a **Static Residential Proxy** via **v2rayN** on Windows to achieve a more secure network access environment.

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

### 1. Preparation

**System and Software Requirements**

* **Operating System**: Windows (this tutorial uses Windows as an example)
* **Installed Software**: v2rayN (latest version)

**Required Proxy Information**

Obtain the static residential proxy information from [JollyProxy](https://www.jollyproxy.com/):

* Server address
* Port number
* Username
* Password

### 2. v2rayN Configuration

**Add a Subscription Group**

1. Open the v2rayN software.
2. Find the **Subscription Group** option in the top menu bar.
3. Click **Add**.
4. Fill in the group information:
   * **Group Name**: A custom group identifier
   * **Pre-proxy**: Select an overseas node (used to connect to the overseas environment)
   * **Landing Proxy**: Fill in the JollyProxy proxy information

<figure><img src="https://779989668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwsS3NgJFgFQvWFmv0zaY%2Fuploads%2FAUkgxkIHjLWxEZ8PmNwH%2Fimage.png?alt=media&#x26;token=71a91825-2d4e-4c02-92dd-bec778896a00" alt=""><figcaption></figcaption></figure>

**Add Proxy Configuration**

1. Select the group you just added.
2. Find the **Configuration Items** option in the top menu bar.
3. Select the protocol: **HTTP Proxy** or **SOCKS Proxy**.
4. Fill in the proxy information obtained from JollyProxy:
   * **Address**: Server address
   * **Port**: Proxy service port number
   * **Username**: Proxy account
   * **Password**: Proxy password

<figure><img src="https://779989668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwsS3NgJFgFQvWFmv0zaY%2Fuploads%2FW1WxtuVHBod6pwOI8ZxO%2Fimage.png?alt=media&#x26;token=bc17a245-2100-4cff-bd1b-2b4ad8e03703" alt=""><figcaption></figcaption></figure>

<figure><img src="https://779989668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwsS3NgJFgFQvWFmv0zaY%2Fuploads%2Fn5Hc3iOv7HERFDiRdoQe%2Fimage.png?alt=media&#x26;token=d50c17b2-dc11-4aa9-ae07-87a9776b933f" alt=""><figcaption></figcaption></figure>

After saving the configuration, you can view the added proxy in the node list.

<figure><img src="https://779989668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwsS3NgJFgFQvWFmv0zaY%2Fuploads%2FseLLald9hNzBKWdwVHPe%2Fimage.png?alt=media&#x26;token=2e9d2b0b-1bb1-49fa-9e84-98779b190540" alt=""><figcaption></figcaption></figure>

### 3. Enable the System Proxy

After completing the proxy configuration:

1. Select the JollyProxy proxy you just added in the v2rayN node list.
2. Right-click the node and select **Set as Active Server**.
3. Return to the v2rayN main interface.
4. Enable **System Proxy**.
5. Select the mode **Auto Configure System Proxy**.

Once enabled, Windows system network traffic will be routed through the proxy set in v2rayN.

### 4. Test the Proxy Connection

In v2rayN:

1. Select the configured JollyProxy proxy node.
2. Click **Test Server Latency**.
3. Check the proxy connection status.

If latency information is displayed normally, the proxy configuration is successful.

<figure><img src="https://779989668-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwsS3NgJFgFQvWFmv0zaY%2Fuploads%2FObmufIRJuPqZhZFNGldF%2Fimage.png?alt=media&#x26;token=471d974f-09d5-4bcf-8a71-76584618e825" alt=""><figcaption></figcaption></figure>

**Verification Method**

Open a browser and visit an IP detection website (such as ipinfo.io) to confirm that the displayed IP address matches the static residential proxy you configured.

### Notes

1. **Usage Notice**: JollyProxy proxies must be used in an overseas network environment. Please configure the overseas network environment in advance.
2. **Software Coordination**: Ensure that v2rayN and related proxy software are configured correctly to avoid functional conflicts.
3. **Traffic Path**: The system traffic path is: Application → v2rayN → Overseas Node → Target Website.
4. **Performance Impact**: Chained proxies may slightly increase latency. It is recommended to choose a low-latency egress node.

> You have now completed configuring the JollyProxy static residential proxy separately in v2rayN and can access the target network environment through the 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/v2rayn.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.
