# Proxies

Proxies are essential for most MVS Web modules. They route your Telegram connections through different IP addresses, preventing blocks and bans that would happen if all traffic came from a single IP.

![Proxy Lists](/files/h5UTNK16zVE47m6gS4kg)

## Proxy Lists Page

The Proxy Lists page shows all your saved proxy lists with their names, number of proxies, and creation dates. From here you can:

* **+ Add List** (top right) -- create a new proxy list
* **Edit** (pencil icon) -- modify an existing list
* **Delete** (trash icon) -- remove a list

## Creating a Proxy List

1. Click the **+ Add List** button in the top right
2. Enter a **name** for the list (e.g., "Mobile USA", "Datacenter EU", "Residential India")
3. Paste your proxies in the text area, one per line
4. Save the list

## Proxy Formats

You can enter proxies in any of these formats:

```
host:port:username:password
```

```
socks5://username:password@host:port
http://username:password@host:port
https://username:password@host:port
```

### Supported Protocols

| Protocol   | Description                                                       |
| ---------- | ----------------------------------------------------------------- |
| **SOCKS5** | Best compatibility with Telegram. Recommended for most use cases. |
| **HTTP**   | Standard HTTP proxy. Works but SOCKS5 is preferred.               |
| **HTTPS**  | HTTP proxy with TLS encryption.                                   |

{% hint style="info" %}
If you are unsure which protocol to use, go with **SOCKS5**. It works best with Telegram.
{% endhint %}

## Using Proxies with Modules

Every module page has a **Select proxy...** dropdown at the top. Before starting a task:

1. Click the proxy dropdown
2. Select a proxy list
3. Start the task

Proxies are distributed evenly across worker threads using **round-robin rotation**. If you have 10 proxies and 20 threads, each proxy will be used by 2 threads.

{% hint style="warning" %}
**Most modules require proxies.** Running registration, checking, or other operations without proxies will likely result in IP bans from Telegram. Always select a proxy list before starting a task.
{% endhint %}

## Rotational (Backconnect) Proxies

If you use a rotational proxy service where the same `host:port` gives you a different IP on each connection:

* Add **a single proxy entry** to the list
* All worker threads will connect through the same address
* The proxy provider handles IP rotation automatically

This is the simplest setup for mobile or residential proxy services.

## Tips for Proxy Management

* **Name your lists descriptively** -- use country codes or provider names (e.g., "ind", "za", "froxy ZA")
* **Separate by country** -- create one list per country if you register accounts from different regions
* **Test your proxies** -- if you see many connection errors in task logs, your proxies may be dead or slow
* **Keep lists updated** -- remove dead proxies and add fresh ones regularly

For a complete guide on proxies, see [Working with Proxies](/mvs-docs/guides/proxy-guide.md).


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://mvs-3.gitbook.io/mvs-docs/settings/proxies.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.