# Add and sign in X accounts

> Add proxies, add an X account to a VPS, sign it in through Remote view, and understand its browser profile and test mode.

Source: https://x.builera.app/docs/en/x-accounts
Last checked: 2026-10-24

## Before you start {#before-you-start}

- A paired VPS (see [VPS & agent](/docs/en/vps-and-agent)).
- One proxy for each X account. A proxy belongs to one X account at a time.
- Only add your own X accounts, or X accounts whose owners have allowed you to use them.

## Add proxies {#add-proxies}

1. Go to **Proxy → Add proxies**.
2. Paste one proxy per line. The dialog shows how each line was read before you add them.
3. Add them, then use **Check all** (or check selected ones) to test them.

What a failed check means:

| Message | Meaning | What to do |
|---|---|---|
| **Can’t connect to the proxy.** | The proxy didn't answer. | Check that it hasn't expired and that the address and port are right. |
| **The proxy rejected the username or password.** | Wrong proxy credentials. | Fix the username or password. |
| **Incorrect proxy type (HTTP or SOCKS5).** | The proxy speaks the other protocol. | Change the type. |
| **Pin mismatch: expected …, measured …** | The proxy now exits from a different IP or location than the one its X account was set up with. | Fix the proxy so it exits where it did before, then check again. The X account waits until then. |

A proxy problem is not an X account problem: the X account's jobs simply wait with **Proxy error or IP changed** until the proxy passes its check.

## Add one X account {#add-one-x-account}

1. Go to **X accounts → Add X account**.
2. **VPS** — choose the machine that will run this X account.
3. **Proxy** — choose an unused proxy.
4. **Details** — enter an **Account label** (a name for you, not the @handle), the **X account age** and the **Time zone** the account normally lives in.
5. **Browser profile** — review the profile X-Buddy created for this X account, then add it.

To add many X accounts from a file, use **Bulk import X accounts** — see [Import X accounts in bulk](/docs/en/import-accounts).

## The browser profile {#the-browser-profile}

Every X account gets exactly one browser profile (fingerprint) when it is added. It is stored by X-Buddy, matches the proxy's location and the time zone you chose, and **never changes or rotates** — every time Chrome opens for this X account, it looks like the same device. Two X accounts never share a profile, so several X accounts on one VPS don't look like one machine.

## Test mode (no proxy) {#test-mode-no-proxy}

**Test mode (no proxy)** lets an X account use the VPS's own network. It is meant for trying X-Buddy out. Don't use it for real X accounts: they would all share the VPS's IP.

## Sign in through Remote view {#sign-in-through-remote-view}

1. Open the X account and choose **Open Remote view**. You see this X account's Chrome on your VPS, live, inside X-Buddy.
2. Type the X username and password into the page yourself.
3. If X asks for a 2FA code or other verification, complete it yourself. **Paste text (2FA code…)** pastes text into the remote page.
4. When X's home page appears, X-Buddy detects the sign-in and saves the handle and profile photo.

While Remote view is open, automated jobs **for this X account** wait (**Remote viewing active**). Other X accounts keep working. Close Remote view when you're finished.

> [!IMPORTANT]
> Remote view is encrypted per session (AES-GCM), and the X-Buddy server creates the session key — so the server **can** know it. It is not end-to-end encrypted. Everything you see and type in Remote view, including passwords, travels this way.

X-Buddy never solves captchas or X verification for you. If X shows one during automated work, the X account stops with **Verification required** and you finish it in Remote view.

## X Chat passcode {#x-chat-passcode}

X's encrypted chat (X Chat) asks for a passcode. An Owner or Manager can save it for an X account in the X account's **Inbox** tab; it is stored encrypted and never shown again. With it, X-Buddy unlocks X Chat by itself before sending messages. If X says the saved passcode is wrong, X-Buddy stops trying (so X Chat doesn't lock) until someone enters the right one. Without a saved passcode, unlock X Chat yourself in Remote view.

## Related {#related}

- [Limits, run hours & safety](/docs/en/limits-and-safety)
- [Troubleshooting](/docs/en/troubleshooting#common-problems)