# Re-Authorization

The Re-Authorization module creates fresh sessions for your existing accounts. It logs in using the current session, generates a new authorization key, and replaces the old session. This is useful when sessions become stale or when you want to change the platform (e.g., from iOS to Desktop).

![Re-Authorization settings](/files/IBbn9pnWXn0HlFp11mp1)

## Settings Reference

### General Settings

| Setting                | Description                                                                                                                                                                         |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Threads**            | How many accounts to re-authorize at the same time. Default: 5.                                                                                                                     |
| **Timeout**            | How long to wait for each re-authorization (seconds). Default: 120.                                                                                                                 |
| **Terminate Sessions** | If enabled, all other active sessions on the account are terminated after re-authorization. Only the new session remains. Old inactive sessions are also removed from the database. |
| **2FA**                | Change or set a 2FA password during re-authorization. **OFF** = keep current 2FA, **Random** = set a random password, **Custom** = set a specific password.                         |
| **2FA Password**       | Only visible when 2FA is set to "Custom". Enter your desired password (3-12 characters, letters and numbers only).                                                                  |

### Session Settings

| Setting             | Description                                                                          |
| ------------------- | ------------------------------------------------------------------------------------ |
| **Language Code**   | Language code for the new session (e.g., `en`, `ru`, `de`). Default: `en`.           |
| **System Language** | System language code for the new session (e.g., `en-US`, `ru-RU`). Default: `en-US`. |

### Desktop Devices

| Setting     | Description                                                                                                                                                                                                  |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Devices** | Custom device pool for new sessions. Enter one device per line in the format: `Model,System Version` (e.g., `Z790 MB,Windows 11 x64`). If left empty, random devices from the built-in device list are used. |

## How to Use

1. Go to **Re-Authorization** in the sidebar
2. Set the number of **Threads**
3. Choose whether to **Terminate Sessions** (recommended if you want clean accounts)
4. Optionally set **2FA** to change the password
5. Select a **Proxy list**
6. In the **Accounts** section, select the accounts you want to re-authorize
7. Click **Start**

{% hint style="warning" %}
Re-authorization creates a **new session** and marks the old one as **replaced**. The old session will no longer work. Make sure you actually want to refresh these sessions before starting.
{% endhint %}

## Understanding the Results

| Result                             | What It Means                                                                                                              |
| ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **REAUTHORIZED**                   | New session created successfully. The old session is marked as replaced.                                                   |
| **2FA\_NO\_PASSWORD / 2FA\_WRONG** | The account has 2FA enabled but the stored password is wrong or missing. The 2FA validity flag is updated in the database. |
| **FROZEN**                         | Account is restricted. All sessions are marked as frozen.                                                                  |
| **BANNED / DEACTIVATED**           | Account is banned. All sessions are marked accordingly.                                                                    |
| **OLD\_SESSION\_DEAD**             | The current session is dead and cannot be used for re-authorization. Only this session is affected.                        |

{% hint style="info" %}
If you see many **2FA\_NO\_PASSWORD** errors, it means the stored 2FA passwords are incorrect. You can use the [2FA Reset](/mvs-docs/modules/twofa-reset.md) module to request a password reset, or update the passwords manually in the account details.
{% endhint %}


---

# 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/modules/reauthorizer.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.