TTMT Docs

Appearance

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 — almost always MetaAPI Cloud, and everything on this page assumes it. TTMT keeps a single shared connection to your broker per account and manages it for you; you don't open or juggle connections yourself. (A small number of accounts are on a self-host provider in limited preview — see Self-host providers.) Connection problems here mean trades cannot be executed.

Authentication Failed ​

Problem: You entered your login details, but the connection stays red or shows "Auth Failed".

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.

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 — 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. 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 dashboard says "Connected" 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 "syncing" or Degraded state right after connecting is normal — see Market-closed and quiet-hours idle below for when a quiet connection is expected rather than broken.
  3. Symbol mismatch: If the trade was placed but uses a symbol that is not available on your broker, check the 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: Your broker connection cycles between green and red 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 solid red rather than cycling, that is not flapping -- it is the sustained-outage case covered next.

Market-closed and quiet-hours idle ​

Problem: Your connection dot goes yellow (Degraded), 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 and TTMT marks the connection Degraded — that's a neutral, expected state, not a fault. 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. A yellow dot on a Sunday is almost always just the closed market.
  2. Wait for reopen. The connection returns to Healthy 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.

The one to worry about is a red dot during market hours, not a yellow dot 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 below.

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 banner appears reading "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 connection light to turn green 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 red streak 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 and contact support.

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.

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.

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.

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, reconnect from Settings > Profile > Reconnect Telegram in your TTMT dashboard.

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.