---
url: /troubleshooting/connection-issues.md
description: >-
  Fix MetaTrader authentication failures, unconfirmed or refused broker logins,
  Telegram session drops, sync problems, and frequent disconnects — plus what a
  market-closed idle connection and a paused instance actually mean.
---

# Connection Issues

TTMT maintains two connections: one to your MetaTrader account (via your broker) and one to your Telegram account (via the Telegram API). This page covers troubleshooting for both.

## Broker Connection Issues

TTMT connects to your MetaTrader account through a **provider**: usually **TTMT Direct** for MT5 accounts on brokers TTMT supports, **MetaAPI Cloud** for the rest — see [Connection providers](/accounts/self-host) to tell which one an account uses. TTMT keeps a single shared connection to your broker per account and manages it for you; you don't open or juggle connections yourself. The sections below apply to both providers, except the three login cards (**Login not confirmed**, **Broker refused login**, **Login status unavailable**), which appear only on TTMT Direct accounts. Connection problems here mean trades cannot be executed.

### Authentication Failed

**Problem:** You entered your login details, but the connection does not come up. The health word in the header stays on **Password?**, **Login?**, **Login** or **Offline**.

**Cause:** Incorrect credentials or server selection.

**Fix:**

1. **Wrong password**: Copy and paste the password directly from your broker email to avoid typos. Check for hidden spaces at the beginning or end.
2. **Investor password instead of Master**: You must use the **Master Password** (also called the Trading Password). The Investor/Read-Only password does not allow trade execution.
3. **Wrong server**: Brokers often have many servers (e.g., `ICMarkets-Live01`, `ICMarkets-Live02`). Open your MT4/MT5 app and check **Settings** or **About** to see exactly which server your account is on.
4. **Wrong platform**: Make sure you selected MT4 if your account is MT4, or MT5 if it is MT5. They are not interchangeable.

### Login not confirmed

::: info TTMT Direct accounts only
The three cards in this section and the next two — **Login not confirmed**, **Broker refused login** and **Login status unavailable** — appear only on accounts using the [TTMT Direct provider](/accounts/self-host). Accounts on MetaAPI Cloud do not show them.
:::

**Problem:** The account's status reads **Login not confirmed**, and a card says "We couldn't confirm your broker login".

**Cause:** Your broker closed the connection right after TTMT sent your login, three times in a row. The broker gave no answer either way, so TTMT cannot tell you whether the login was accepted. This is often a broker-side problem. It does not mean your password is wrong.

The same card covers two close relatives, and it tells you which one you have:

| What the card says | What happened |
|:--|:--|
| "Your broker closed the connection right after TTMT sent your login, three times in a row." | No answer from the broker at all. |
| "Your broker accepted the login, but the session did not start three times in a row." | Your password was accepted. The session failed afterwards. |
| "Your broker accepted the login, then dropped the session within minutes, three times in a row." | Your password was accepted. Another login on the same account, or a broker-side limit, can cause this. |

**What TTMT does:** it slows down, so your account is not hammered with logins. It now retries about every two hours while the market is open, and again within two hours of the market opening. Where the broker accepted the login but the session did not start, it retries about once an hour while the market is open. Each of these is an attempt. Whether it succeeds is up to your broker, so TTMT does not promise a time by which the account is back.

**Fix:**

1. **Click Try now** if you have reason to think the broker is ready. It makes one login attempt right away, and the card updates within a minute. It does not restart your trading connection.
2. **Check your broker.** Log in to the same account and server in your MT5 app. If that fails too, the problem is on the broker's side, and their support is the place to ask.
3. **Use Update password only if you changed it.** The card offers **Update password** only where the broker closed the connection right after the login was sent. If your password has not changed, entering it again does not help.

**Try now** is refused in a few situations, and the card says which:

* "Your broker session is up — nothing to retry": the connection is already live.
* "A trade is being confirmed — try again in a few seconds": TTMT will not start a login while an order is in flight.
* "Already trying", with a countdown: an attempt is under way, or you tried within the last minute.
* "Couldn't start an attempt — try again in a minute": the request did not get through.

### Broker refused login

**Problem:** The account's status reads **Broker refused login**, and a card says "Your broker refused this login".

**Cause:** Your broker gave a definitive answer, and it is not about your password. The card names it:

| What the card says | What to do |
|:--|:--|
| "Your broker says this account number does not exist or is closed. Demo accounts often expire after a few weeks." | Check the account with your broker. An expired demo needs a new account. |
| "Your broker says this account has moved to a different server." | Find the new server in your MT5 app or your broker's email. |
| "Your broker says this account belongs to a different server." | Check the exact server name in your MT5 app. |
| "Your broker requires a one-time code for this account, which TTMT cannot enter." | TTMT cannot enter the code. Ask your broker about the login requirements for this account. |

In every one of these cases TTMT has stopped trying. There is no automatic retry, because repeating a login the broker has refused does not change the answer.

**Fix:**

1. Sort out the cause with your broker, using the table above.
2. Click **Try now**. It makes one login attempt right away, and the card updates within a minute.
3. If the account is gone for good, click **Remove account**.

A wrong password is a different case and does not show this card — see [Authentication Failed](#authentication-failed).

### Login status unavailable

**Problem:** The account's status reads **Login status unavailable**, and a card says "We can't read your broker login status right now".

**Cause:** TTMT lost the connection details it needs to show whether your broker accepted the login. This says nothing about your broker's answer or your password. TTMT checks again automatically every few minutes, and your trading settings are unchanged.

**Fix:**

1. Click **Check now**. It reads your connection status again. It does not log in.
2. If the check does not show a live session, **Try a login now** appears. It makes one login attempt right away.
3. If the check itself fails, the card offers **Contact support**.

### Too Many Connection Attempts

**Problem:** After several failed attempts you see "Too Many Attempts", and TTMT stops letting you try again for a while.

**Cause:** Your broker rejected the login details, and after repeated rejections the connection provider pauses further validation for that account. This is the broker-side equivalent of Telegram's [FLOOD\_WAIT](#flood-wait-rate-limiting) — a protection, not a fault. It applies to the **account**, not to the password you typed, so correcting the password and retrying straight away still meets the same pause.

**Fix:**

1. **Wait for the time shown.** When the provider tells us how long the pause lasts, TTMT shows that actual time. If no time is shown, we genuinely do not have one — wait a few minutes rather than guessing.
2. **Do not keep retrying.** Every rejected attempt counts against the same limit, so retrying lengthens the wait instead of shortening it.
3. **Fix the details before your next attempt.** Check the Master (not Investor) password, the exact server name as it appears in your MT4/MT5 app, and the platform — see [Authentication Failed](#authentication-failed). One correct attempt is worth more than ten guesses.

### "No Answer Yet"

**Problem:** A connection attempt ends with "No Answer Yet" instead of a specific error.

**Cause:** Setting up the connection involves your broker validating the login, and that can take minutes. When no verdict arrives in time, TTMT says so plainly rather than naming a cause it did not observe.

**Fix:**

1. **Try again.** A genuinely slow broker usually succeeds on a later attempt.
2. **Re-check your details.** Many attempts that end this way turn out to be a wrong password, server or platform.
3. **Do not re-submit while it is still working.** The connection screen keeps showing progress while your broker is being contacted. Submitting again starts a second attempt and can trigger the pause described above.

### Account Not Syncing

**Problem:** The header health word reads **OK** but new trades are not showing up.

**Cause:** TTMT uses a Magic Number to identify its own trades.

**Fix:**

1. **Manual trades are filtered**: TTMT only shows trades it placed. If you opened a trade manually on your phone, it will not appear in the TTMT dashboard unless you explicitly use the Sync feature.
2. **Give a fresh connection a moment**: When an account has just connected or reconnected, prices and positions take a little time to settle. A short **Connecting** or **Starting** state right after connecting is normal. **Stalled** is a warning: if it stays, see below. For a quiet weekend or overnight connection, see [Market-closed and quiet-hours idle](#market-closed-and-quiet-hours-idle).
3. **Symbol mismatch**: If the trade was placed but uses a symbol that is not available on your broker, check the [Symbol Mapping](/accounts/symbol-mapping) settings.
4. **Setup stuck for 10+ minutes**: If an account is genuinely stuck in "Deploying" or "Setting up" long past the usual minute or two, contact support rather than disconnecting it. Disconnecting an account with open positions leaves those positions unmanaged on your broker (TTMT can no longer move their SL or TP) — so it's not a safe first move. Support can rebuild the connection without putting your open trades at risk.

### Frequent Disconnects

**Problem:** The header health word for your broker connection cycles between **OK** and **Reconnecting** or **Offline** repeatedly.

**Cause:** Broker server instability, especially during high-impact news events. This is transient flapping, not a sustained outage.

**Fix:**

1. **Wait it out**: This is often temporary during major economic releases (NFP, FOMC, etc.). The connection will stabilize once volatility calms down.
2. **Check broker status**: Some brokers have status pages or Telegram channels where they announce server issues.
3. **Persistent disconnects (24+ hours)**: Contact support so we can check region latency and connection health for your specific broker server.

If the connection stays down rather than cycling, that is not flapping -- it is the sustained-outage case covered next.

### Market-closed and quiet-hours idle

**Problem:** The health word shows **Closed**, or the account looks idle, during the weekend or overnight.

**Cause:** This is usually **not** a lost connection. When your broker's market is closed, no price ticks arrive, so quotes go stale. TTMT shows **Closed** (muted) while the market is closed. A reopening countdown on the dashboard is a display aid telling you when the market comes back, not a promise that anything is broken.

**Fix:**

1. **Check whether the market is actually open.** Forex closes over the weekend and some instruments have their own sessions. **Closed** on a Sunday is almost always just the closed market. If it says **Stalled** while the market is open, treat it as a real feed problem.
2. **Wait for reopen.** The word returns to **OK** on its own when ticks start flowing again. There is nothing to reconnect.
3. **Don't expect off-hours signals to trade.** A signal that arrives while the market is closed is skipped immediately — it is **not** queued to fire at reopen. See [Trade Execution Issues](/troubleshooting/trade-execution-issues#the-signal-was-skipped-not-queued).

The one to worry about is **Offline** or a **Login** word during market hours, not **Closed** while the market is closed.

### "Connection lost" right after opening the dashboard

**Problem:** You switch back to the dashboard — after locking your phone, changing apps, or leaving the tab in the background — and for a moment it shows *Connecting...* or *Connection lost*, then goes green again a second or two later.

**What it means:** Nothing was wrong with your broker or your trading. Phone and desktop browsers pause a tab they think you have stopped looking at, which includes the live data feed the dashboard uses. Reopening the tab wakes it, and it takes a moment to catch up. Your account stayed connected the entire time, and signals kept being executed — none of that runs in your browser.

**What to do:** Nothing. The dashboard now stays quiet through a brief catch-up rather than alarming, and reconnects immediately when you return, so in normal use you should not see this at all.

If the message persists for more than a few seconds, it is no longer a browser catch-up — the dashboard will say it is reconnecting to your account and show you when it last had fresh data. If it lasts minutes, see [Connection Down for 5+ Minutes](#connection-down-for-5-minutes-the-reconnect-banner) below.

::: info Two different things can be "down"
The dashboard's own connection to TTMT, and TTMT's connection to your broker. Only the second one affects your trades. The dashboard now names which one it means: a message about *reconnecting to your account* is about the first, and it does not imply anything about your broker.
:::

### Connection Down for 5+ Minutes (the Reconnect banner)

**Problem:** A red banner appears: "Your trading connection looks down. We haven't heard from your broker for about 5 minutes. Reconnect to restore live trading."

**Cause:** TTMT has not received a price update from your broker for about five continuous minutes. The live link went quiet and stayed quiet, rather than cycling.

**Fix:**

1. Click **Reconnect** in the banner. This restarts your trading connection. It usually takes around 30 seconds, up to about a minute if your broker is slow to respond.
2. Wait for the header health word to read **OK** again.

**What happens to your open trades during a reconnect:** your broker keeps enforcing your existing SL and TP the whole time -- your positions are not abandoned. Reconnect re-establishes TTMT's live link to your broker. It does not close or modify anything.

This step is user-in-the-loop by design. TTMT keeps trying to reconnect automatically underneath, but after a sustained outage it asks you to trigger the restart rather than silently retrying. If clicking Reconnect does not restore the connection, treat it as a [persistent disconnect](#frequent-disconnects) and contact support.

::: info Automatic vs. manual reconnection
Brief drops recover automatically -- TTMT refreshes connections periodically and cleans up idle ones without any action from you. A sustained outage is different: when your broker goes quiet for 5+ minutes, the Reconnect banner above appears so you can trigger the restart. Use it when you see it.
:::

::: info The Reconnect banner and the login cards are different situations
The Reconnect banner is unchanged. The **Login not confirmed**, **Broker refused login** and **Login status unavailable** cards (TTMT Direct accounts only) cover a different situation: your broker would not confirm or accept the login. **Reconnect** restarts your trading connection. **Try now** on a login card makes one login attempt and restarts nothing. See [Login not confirmed](#login-not-confirmed).
:::

TTMT also monitors accounts that repeatedly fail to connect during market hours and flags them for review automatically. There is nothing extra you need to watch for here.

::: info Not a connection drop: a paused instance
If your whole dashboard is offline — not one account's connection, but the entire service showing a paused or reactivation screen — that's a different situation from a broker disconnect. Your trading service can be paused at the infrastructure level (for example, after a long gap in use or an incomplete onboarding), which preserves all your data and config and can be reactivated. That is **not** the same as a billing suspension. See [Instance pause and reactivation](/troubleshooting/instance-pause-reactivation).
:::

## Telegram Connection Issues

### Session Expired

**Problem:** Your Telegram connection dropped and you need to re-enter your phone number and verification code.

**Cause:** Your Telegram connection session was invalidated, usually because you terminated the session from your Telegram app.

**Fix:**

1. Go to **Telegram App > Settings > Devices** (or **Privacy & Security > Active Sessions**).
2. Look for a session named **"TTMT · telegramtometatrader.com"** (older sessions may still show as "TTMT User Service" until they reconnect).
3. **Do NOT terminate this session.** It is how TTMT reads your channel messages.
4. If the session is already gone, press **Reconnect Telegram** in the banner at the top of the Channels page, or **Reconnect Now** in the Telegram control in the header. (**Sign in with Telegram** on your Profile page is only for logging in and does not reconnect this session.)

::: warning
Terminating the TTMT session is the number one cause of Telegram disconnections. If you regularly clear all sessions from Telegram, keep the "TTMT · telegramtometatrader.com" session.
:::

### The Login Code Never Arrives

**Problem:** You pressed **Send Code**, TTMT says the code was sent to your Telegram app, but nothing shows up.

**Cause:** Telegram delivers login codes for third-party apps only as an in-app message (never SMS), and it sometimes holds them back for a number for a few hours. Asking again repeatedly makes the hold last longer.

**Fix:**

1. Open the chat named **"Telegram"** (blue check) on **every** device where you are logged in — the code is a message there, not a notification you might have dismissed.
2. Wait for the help panel on the code step (it opens after a minute) and follow it.
3. On a computer, choose **Scan a QR code instead** — it connects without a code. On a phone, choose **Continue on a computer** to get a link by email.
4. If TTMT says Telegram is pausing codes for your number, choose **Remind me to try again** and come back in a few hours. Do not keep requesting codes.

### "There's no Telegram account on this number yet"

**Problem:** TTMT shows this on the phone step.

**Cause:** Telegram has no account registered to that number, so there is nothing to log in to.

**Fix:** Create the account in the Telegram app first (it takes a minute), then come back and connect. If you already have an account, check the country code — the number must be the one Telegram knows.

### "Telegram requires an email login" / "Telegram is asking for a Premium purchase"

**Problem:** Telegram wants something other than a login code for your account.

**Fix:** These are Telegram-side requirements for your account. Log in from the official Telegram app on your phone first, then connect TTMT — on a computer, **Scan a QR code instead** skips the code entirely.

### FLOOD\_WAIT Rate Limiting

**Problem:** You see a "FLOOD\_WAIT" error when trying to connect or reconnect Telegram.

**Cause:** Telegram rate-limits authentication attempts. If you tried to connect too many times in a short period, Telegram enforces a cooldown.

**Fix:**

1. Wait for the countdown timer shown in the error message to expire. This can range from a few seconds to several hours depending on how many attempts were made.
2. Do not keep retrying -- each failed attempt extends the cooldown. TTMT also caps code requests itself (3 per 30 minutes, 5 per day per number) for the same reason.
3. Once the timer expires, try connecting again with the correct phone number — or, on a computer, use **Scan a QR code**, which needs no code.

### Two-Factor Authentication (2FA) Issues

**Problem:** You have 2FA enabled on your Telegram account and the connection is failing.

**Cause:** TTMT needs your cloud password (the 2FA password you set in Telegram) to authenticate.

**Fix:**

1. When prompted during connection, enter your **Telegram Cloud Password** (the password you set under Telegram > Settings > Privacy & Security > Two-Step Verification).
2. This is different from your phone's lock screen password or your TTMT account password.
3. If you forgot your cloud password, you must reset it through the Telegram app first.

### Telegram Connection Keeps Dropping

**Problem:** The connection drops every few days even though you have not terminated the session.

**Cause:** This can happen if your Telegram account is used on many devices simultaneously, or if Telegram's servers are experiencing issues.

**Fix:**

1. Verify the "TTMT · telegramtometatrader.com" session is still listed in your Telegram app.
2. If you have 2FA enabled, ensure the cloud password has not changed since you connected.
3. Reconnect from the TTMT dashboard. A fresh session is typically more stable.
4. If drops persist, contact support with your approximate timezone so we can check server-side logs.

## Related pages

* [Trade Execution Issues](/troubleshooting/trade-execution-issues)
* [Connection providers](/accounts/self-host)
* [Instance pause and reactivation](/troubleshooting/instance-pause-reactivation)
* [Account details](/accounts/account-details)
* [Symbol Mapping](/accounts/symbol-mapping)
