MT4 and MT5 Symbol Suffixes: Fixing Unknown Symbol Errors
EURUSD.pro, EURUSDm, XAUUSD.r. Why a one-character mismatch rejects OrderSend outright, why Market Watch visibility is a precondition, and how to map a TradingView ticker onto your broker symbol.
The One-Character Problem
Your alert fired. Your bridge is online. The Experts tab says the order was received. And MetaTrader rejected it with an unknown symbol error, because your server lists the instrument as EURUSDm and the order asked for EURUSD.
MetaTrader does no fuzzy matching whatsoever. There is no nearest-match fallback, no case-insensitive lookup, no stripping of trailing characters. A symbol name is an exact string key into the server instrument list, and one character off is the same as asking for an instrument that does not exist. That is the entire bug, and it accounts for a large share of every MetaTrader automation support thread ever written.
This page covers both MT4 and MT5, because the decoration problem is identical on both and only the error codes differ. It applies to any bridge that submits through OrderSend, not just ours.
The Prefix and Suffix Taxonomy
Brokers decorate symbol names so that several account books can live on one server. A raw-spread book, a standard book, a cent account and a swap-free book can all carry EURUSD with different spreads, commissions and contract sizes, so each version gets its own name. The decoration is therefore account-type specific, not just broker specific: two traders at the same broker can need different suffixes.
| Form | Example | What to enter | Notes |
|---|---|---|---|
| Bare | EURUSD | Suffix empty, prefix empty | The default. Many ECN and institutional books ship undecorated names. |
| Letter suffix | EURUSDm | Suffix = m | Common on micro and cent account books. Also seen as c, z, e. |
| Dotted suffix | EURUSD.pro | Suffix = .pro | The dot is part of the name. Also .a, .r, .ecn, .raw, .stp. |
| Trailing dot | EURUSD. | Suffix = . | Easy to miss entirely because the dot looks like punctuation in a screenshot. |
| Underscore suffix | EURUSD_i | Suffix = _i | Used to separate instant-execution books from market-execution ones. |
| Letter prefix | mEURUSD | Prefix = m | Rarer than suffixes, but real. Prefixes go on the front of the whole name. |
| Category prefix | FX_EURUSD | Prefix = FX_ | Multi-asset servers grouping forex apart from indices and metals. |
| Metals decorated | XAUUSD.r | Suffix = .r | Gold and silver take the same decoration as the pairs on the same book. |
| Renamed metal | GOLD | Not a suffix at all | Some servers rename the instrument rather than decorate it. Prefix and suffix cannot fix this. Rename the Ghost ticker instead. |
Do not trust a published broker-to-suffix list, including this one, as an authority for your own account. Read the exact string off your own Market Watch. It is the only source that cannot be wrong.
Why One Character Breaks OrderSend
The symbol is a key, not a search term
Both MT4 and MT5 resolve a symbol name by exact lookup against the server instrument list. If the key misses, the call does not degrade gracefully: it fails before any trade logic runs. Nothing downstream gets a chance to correct it.
MT4 fails at the symbol layer
On MT4 the failure surfaces as error 4106, unknown symbol, from the market-info call the EA makes before it can build the order. The order never reaches the trade server, so there is no broker-side record of the attempt.
MT5 fails in more than one place
MT5 separates unknown symbol (4301) from symbol not selected (4302), and then reports a failed submission as 4756 when the request cannot be sent. The same root cause can therefore show up under three different numbers depending on where it breaks.
Rejections come back honestly
When the terminal rejects an order, the Ghost bridge EA reports the rejection and the broker error text back to Ghost rather than silently swallowing it. A rejected entry is marked rejected, not left looking like a fill that never happened.
Market Watch Visibility Is a Precondition
Getting the name right is necessary but not sufficient. MetaTrader only loads full instrument data for symbols that are selected into Market Watch: tick data, contract specification, volume limits, trading permissions. A symbol that exists on the server but is not selected answers as though it is not there at all.
This is why a symbol you can find in the broker Symbols dialog still throws an error when an EA tries to trade it. Selecting it is a trading precondition, not a display preference.
MT4: right-click anywhere in Market Watch and choose Show All, or open the Symbols dialog and enable the instruments you trade.
MT5: open the Symbols dialog (right-click Market Watch, then Symbols), find the instrument in its group, and add it to Market Watch.
Once it is visible, copy the name straight out of the Market Watch column. Do not retype it: a lowercase letter or a missing dot puts you right back where you started.
Error 4106, 4756, and the Rest
| Code | Platform | Meaning | Usual cause |
|---|---|---|---|
| 4106 | MT4 | Unknown symbol | The name passed to the trade call is not on the server list. Missing or wrong decoration. |
| 4301 | MT5 | Unknown symbol | Same cause as 4106 on the MT5 side. |
| 4302 | MT5 | Symbol not selected in Market Watch | The name is right but the instrument was never selected, so no data is loaded. |
| 4756 | MT5 | Trade request sending failed | Generic OrderSend failure. An unresolvable or unselected symbol is a common trigger; invalid volume is the other. |
| 4060 (MT4) / 4014 (MT5) | MT4 and MT5 | WebRequest not permitted | Not a symbol problem. quantcrawler.com is missing from the Expert Advisors URL whitelist, so the EA never even polls. |
4756 is the one that sends people in circles, because it names the symptom rather than the cause. Treat it as a prompt to check two things in order: the symbol name against Market Watch, then the lot size against the broker minimum lot and lot step. Between them those cover most cases.
Setting Prefix and Suffix in the Ghost Bridge EA
Open Market Watch in your terminal and read the exact symbol name for the instrument you trade, including any dot, underscore or trailing character.
Split it into three parts: anything before the six-letter pair is the prefix, the pair itself is the core, anything after it is the suffix. For EURUSD.pro the prefix is empty, the core is EURUSD and the suffix is .pro.
In MetaTrader, right-click the chart the QuantCrawler Bridge EA is attached to, choose Expert Advisors > Properties, and open the Inputs tab.
Fill in SymbolPrefix and SymbolSuffix with those exact strings. Leave either blank if it does not apply. The EA applies them to every symbol before it submits.
Click OK and confirm AutoTrading is still enabled, then fire a test alert and watch the Experts tab for the resolved symbol name.
Set it in one place only
Ghost can also store a prefix and suffix against the broker account itself, and it applies those before the order is queued. The EA then applies its own inputs on top. Fill in both and you will double-decorate: Ghost sends EURUSDm, the EA appends another m, and your broker gets an order for EURUSDmm that does not exist. Use the EA inputs, leave the account-level fields blank, and the chain stays predictable.
Pip Size Runs on the Queued Symbol
This is the part that matters most, and it is the reason a symbol mistake can be worse than a rejected order. Ghost sends stop-loss and take-profit to the EA as pip distances rather than prices, so both ends have to agree on what a pip is. They agree by using the same fixed table, and both apply it with the same rule to the same queued symbol, before the EA adds its own decoration.
| Instrument class | Examples | One pip |
|---|---|---|
| Six-letter pairs ending JPY | USDJPY, EURJPY | 0.01 |
| All other six-letter pairs | EURUSD, GBPAUD | 0.0001 |
| Gold | XAUUSD | 0.1 |
| Silver | XAGUSD | 0.01 |
| Everything else | US30, NAS100 | 1.0 (index points) |
Why the queued symbol matters so much
The currency-pair branch of that table is selected by a leading-six-letter test: if the first six characters of the symbol are letters, it is treated as a pair. EURUSD resolves to 0.0001, and so do EURUSDm and EURUSD.pro, because they also start with EURUSD. The server and the EA apply the identical rule, so a suffix never changes the pip size.
The EA runs that test on the symbol Ghost queued, before it applies its own SymbolPrefix and SymbolSuffix. So decoration configured in the EA inputs is safe: it is applied to the order, not to the pip calculation.
The trap is upstream. If a prefix sits in front of the pair on the Ghost side (in the ticker name or the account-level prefix field), the first six characters are no longer the pair. M.EURUSD falls through to 1.0 index points, and FXUSDJPY is read as a non-JPY pair at 0.0001. Nothing errors and the order goes in with the wrong stop distance. Name your Ghost tickers with the plain TradingView symbol and let the EA add the decoration.
What Ghost Sends and What the EA Submits
1. TradingView ticker arrives
The alert carries whatever your ticker is called. An exchange prefix like OANDA:EURUSD, a slash like EUR/USD, or a dash are all handled: Ghost uppercases the name, drops anything before the colon, and removes slashes, dashes and spaces.
2. Pip size is read from the queued symbol
Pip size is computed from the symbol Ghost queues, which already includes any prefix or suffix you set in Ghost, using the same leading-six-letter rule the EA applies before adding its own SymbolPrefix/SymbolSuffix. A trailing suffix such as EURUSDm still reads as a EURUSD pair; a leading prefix such as M.EURUSD does not.
3. SL and TP become pip distances
Your alert sl and tp are absolute prices. Ghost measures each against the signal price and converts the gap into pips using the pip size of the queued symbol, then queues the order with pip distances rather than levels.
4. The EA decorates and submits
The EA applies SymbolPrefix and SymbolSuffix, submits with OrderSend, then converts the pip distances back into prices against the price it actually filled at. That is why the bracket sits at your intended distance from the real fill rather than from the signal.
A renamed instrument is the one case decoration cannot solve. If your server calls gold GOLD rather than XAUUSD, no prefix or suffix will bridge that, because the core is different rather than decorated. Name the Ghost ticker to match and route your alert at it.
Fix It In This Order
Same Problem, Both Terminals
Symbol decoration is not an MT5 problem or an MT4 problem, it is a MetaTrader problem, and the fix is identical on both. The Ghost bridge ships as two builds (a .mq4 that installs into MQL4 > Experts and a .mq5 that installs into MQL5 > Experts) with the same SymbolPrefix and SymbolSuffix inputs and the same shared pip table on each.
Full walkthroughs for each terminal: TradingView to MT4 and TradingView to MT5. Both cover the install path, the URL whitelist, lot sizing, and the limits of the rail: no trailing stop, no break-even, no resting limit entries, no execution with the terminal closed, and forex and CFDs only, never futures.
Frequently Asked Questions
What causes an unknown symbol error in MT4 or MT5?
The symbol string your EA passed does not exactly match a symbol name on your broker server. MetaTrader does no fuzzy matching at all: EURUSD and EURUSDm are two unrelated instruments as far as the terminal is concerned, and a missing or wrong suffix is enough to reject the order. On MT4 this surfaces as error 4106. On MT5 it is usually 4301 for an unknown symbol or 4302 when the symbol exists but was never selected into Market Watch.
What is MT5 error 4756?
ERR_TRADE_SEND_FAILED. It means OrderSend could not submit the trade request at all, so it is a generic failure rather than a specific diagnosis. It shows up constantly in suffix threads because an unresolvable or unselected symbol is one of the common ways a request ends up unsendable. If you see 4756, check the symbol name against Market Watch first, then check volume against the broker minimum lot and lot step.
Why does the symbol have to be visible in Market Watch?
Because MetaTrader only loads full instrument data for symbols that are selected. A symbol that exists on the server but is not in your Market Watch has no tick data, no contract specification and no trading permissions loaded, so the terminal answers as though it does not exist. On MT4 right-click Market Watch and choose Show All. On MT5 open the Symbols dialog and add the instrument to Market Watch. Selecting it is a precondition for trading it, not a display preference.
Where do I set the prefix and suffix for the Ghost bridge?
In the EA inputs. Attach the QuantCrawler Bridge EA to a chart, open its settings, and fill in SymbolPrefix and SymbolSuffix to match exactly what your Market Watch shows, including the dot if there is one. Set it in one place only: Ghost can also store per-account decoration, and if you fill in both the two get applied on top of each other and you end up sending EURUSDmm.
Does the broker suffix affect my stop-loss distance?
A suffix does not. The server and the EA classify pip size with the same rule, on the symbol Ghost queues before the EA adds its own SymbolPrefix and SymbolSuffix: a symbol starting with XAUUSD or XAGUSD is gold or silver, and any symbol whose first six characters are letters is a currency pair (0.01 when characters four to six are JPY, otherwise 0.0001). EURUSDm and EURUSD.pro both start with EURUSD, so they resolve to 0.0001 just like EURUSD. The risk is a prefix in front of the pair on the Ghost side: then the first six characters are no longer the pair, the pip size can come out wrong, and a 20-pip stop can become a 20-point stop. Name your Ghost ticker with the plain TradingView symbol and let the EA add the decoration.
Why does my broker use a suffix at all?
To run several account types off one server. A raw-spread book, a standard book, a cent account and a swap-free book can all list EURUSD with different spreads, commissions and contract sizes, so the server gives each version its own name. That is also why the decoration is account-type specific rather than broker specific, and why any published broker-to-suffix table goes stale quickly. Read it off your own Market Watch.
My symbol is correct but orders still fail. What else should I check?
Work down the chain. Confirm quantcrawler.com is whitelisted under Tools > Options > Expert Advisors, or WebRequest fails (error 4060 on MT4, 4014 on MT5) with no popup, the EA prints "[QC Bridge] WebRequest BLOCKED" in the Experts tab, and nothing reaches the terminal. Confirm AutoTrading is on and the EA is polling. Confirm the lot size matches the broker minimum lot and lot step, which is a separate invalid-volume rejection. Then confirm the alert itself is firing: TradingView only permits webhook alerts when two-factor authentication is enabled on your account.
Continue Learning
TradingView to MT4 →
Full MQL4 install, whitelisting, and setup walkthrough
TradingView to MT5 →
The MetaTrader 5 side of the same bridge
TradingView Webhook Setup Guide →
How Ghost webhooks work and the full JSON payload reference
Pip Value Calculator →
Check what a pip is worth before you size the trade
Ghost Webhook Automation →
Connect TradingView to 11 brokers
Risk Disclosure: Trading involves substantial risk of loss and is not suitable for all investors. This content is for educational purposes only and does not constitute financial advice.
Last updated: November 2026