Fusion Markets MT5: server names, demo login fix and TradingView setup

Fusion Markets MT5 server names (verified)

Fusion Markets publishes these MT5 server names in the mobile download links of its MetaTrader 5 page (verified 4 October 2026):

The page does not say which account gets the AU pair, so do not guess: copy the server from your Fusion Markets welcome email or the account details in the client area, and register that same string in SignalForge. In MT5 you can also go to File, Open an Account, type Fusion Markets and pick the server from the list.

Can't connect a Fusion Markets demo to MT5? Fix "No connection"

"No connection" or "Invalid account" in the bottom-right corner of MT5 almost always comes from one of these five causes. Work down the list in order:

1. Wrong server

The login dialog often remembers MetaQuotes-Demo or another broker's server. A demo login only connects to a demo server (FusionMarkets-Demo or FusionMarketsAU-Demo, whichever your account details show), never to a live one. If the server is not in the list, use File, Open an Account and search for Fusion Markets.

2. Client area password instead of the MT5 password

The password for the Fusion Markets client area is not the MT5 password. Use the login and password issued for the MT5 account itself; if you are unsure, reset the MT5 password from the client area.

3. The demo has expired

Fusion Markets says on its demo account page that a demo account is active for 30 days (verified 4 October 2026). After that the login stops connecting: open a new demo and log in with the new credentials.

4. Investor (read-only) password

With the investor password the account connects read-only and every order is rejected. Log in again with the master password.

5. Network, VPN or firewall

Corporate networks, VPNs and some firewalls block MT5. Try a phone hotspot: if it connects there, the network is the problem. Right-clicking the connection status in MT5 and choosing Rescan servers also helps after a network change.

How to connect TradingView to Fusion Markets MT5

1. Create your SignalForge account (14-day free trial, no card) and copy your webhook URL from the dashboard.
2. Register your Fusion Markets account in the dashboard with your MT5 login and the exact server string (for example FusionMarkets-Demo while you test).
3. Install the SignalForge EA in that MT5 terminal, drag it onto one chart and switch Algo Trading on.
4. Create the TradingView alert: paste the webhook URL and a JSON message that uses the exact symbol from your Market Watch (Ctrl+M):

{
  "symbol": "EURUSD",
  "action": "buy",
  "lot": 0.1,
  "sl": 30,
  "tp": 60
}

sl and tp are distances in pips by default. Leave lot out to let the EA size the trade with the position size type set in your dashboard (fixed, risk or signal); in fixed-lot mode the EA ignores the alert's lot.

5. Fire a test alert on a demo first and check the order in the Trade tab and the Experts log of MT5.
6. Go live only when the demo order matches what you expected (symbol, lot, SL and TP).

Fusion Markets symbols: check the exact name in your MT5

These are the usual names, not a promise: account types can add a suffix, so copy the symbol exactly as your Market Watch (Ctrl+M) shows it; if one is missing, right-click the list and choose Show All. The SignalForge EA resolves common suffixes on its own (.a .b .i .pro .raw .std .stp m pro #) and partial matches.

Common errors with Fusion Markets and TradingView alerts

These are generic MT5 problems that also appear on Fusion Markets accounts; each link goes to a step-by-step fix.

• Commission not in your backtest. If your TradingView strategy was tuned without commission, add the commission of your Fusion Markets account type to the strategy settings before trusting the results.
• Wrong symbol name or suffix. The alert must name a symbol that exists in your terminal. Suffixes are resolved automatically; aliases on our server only cover GOLD to XAUUSD and SILVER to XAGUSD, so if your MT5 lists gold as GOLD, ask support for a per-account alias. Fix: wrong symbol, lot size or account in MT5.
• Different contract size on gold and indices. One lot of XAUUSD or of an index CFD is not the same exposure on every account. Check the contract size in the symbol specification (right-click the symbol, Specification) before you size by lot.
• Webhook received, but no trade. Usually Algo Trading is off, the EA is not on a chart, or the login registered in the dashboard is not the one logged in. Fix: TradingView webhook not executing in MT5.
• Error 4756 when sending the order. MT5 refused the trade request: invalid stops, volume or margin are the usual causes. Fix: MT5 error 4756.
• Nothing executes after a restart. If MT5 or the PC restarted, the terminal must be running again with the EA on a chart. See what happens when MT5 restarts.

FAQ

What is the Fusion Markets MT5 server name?

Fusion Markets lists FusionMarkets-Demo and FusionMarkets-Live, plus FusionMarketsAU-Demo and FusionMarketsAU-Live, on its MetaTrader 5 page (verified 4 October 2026). Use the exact server shown in your own account details: a demo login only works on a demo server.

Why does my Fusion Markets demo say No connection in MT5?

In order of likelihood: the wrong server is selected, you typed the client portal password instead of the MT5 password, the demo has expired (Fusion Markets says demo accounts are active for 30 days), you used the investor password, or your network blocks MT5. The checklist above walks through each one.

Does SignalForge work on a Fusion Markets demo account?

Yes. Demo and live use the same setup, so test your TradingView alerts on the demo first and switch the login and server when you go live.

Do I need a VPS for Fusion Markets?

No. The EA runs in your own MT5 terminal, so your PC must stay on while you want alerts executed. If you prefer not to, SFCloud runs it for you in a hosted MT5 (UK and France): $9.99/month with the Starter bridge (Starter + SFCloud) or $19.99/month with Trader (Trader + SFCloud). Standalone SFCloud ($6.99/month) is an always-on MT5 in the cloud for manual trading; it does not include the bridge, so it does not execute TradingView alerts.

How fast are TradingView alerts executed?

In our 19-23 September 2026 measurement the median time from webhook to confirmed order was about 0.5 s. The fill itself still depends on your broker and your terminal's connection.