Before troubleshooting your MT5-to-MT5 setup, check the following:
Install through MQL5 Market: Install Local Trade Copier EA MT5© through the same MQL5 account used for the purchase in every MT5 terminal. Copying and pasting the purchased EX5 file between terminals will not work.
Use the correct broker terminal: Whenever possible, use the MetaTrader 5 terminal provided by the broker of each trading account.
Keep each account in its own terminal: Do not switch to another trading account inside a terminal while Local Trade Copier EA MT5© is running. Use separate MT5 terminal installations for the Transmitter and Receiver accounts.
Use the normal trading password on the Receiver: An investor/read-only password cannot be used because the Receiver needs permission to open, modify and close trades.
Check broker symbol names: If the Transmitter uses a dot suffix such as EURUSD.r, Local Trade Copier EA MT5© normally maps it automatically to EURUSD on the Receiver. Non-dot Transmitter suffixes and Receiver suffixes require the appropriate settings in the Receiver EA. Completely different symbol names, such as US500 → SPX500, can be configured using the Special Symbol settings.
This guide covers common MT5 trade copier problems and solutions, including trades not copying, incorrect lot sizes, symbol differences, multiple copied trades, Receiver account restrictions, copying delays, VPS issues and MQL5 Market errors.
If your specific problem is not covered below, please contact me through my MQL5.com profile or company email: info@juvenille-emperor.com. I will be happy to help you review your setup.
Before troubleshooting, I also recommend checking the MT5 to MT5 Trade Copier Installation Guide and Local Trade Copier EA MT5 Settings & Inputs Guide to confirm that your Transmitter and Receiver accounts are configured correctly.
MT5 Trade Copier Not Copying Trades? Start Here
If trades are not copying between your MetaTrader 5 accounts, check these points first:
1. Check the EA installation.
Local Trade Copier EA MT5© should be installed through your MQL5 account in every MT5 terminal. Do not copy the purchased ex5 file manually between terminals.
2. Check the Transmitter and Receiver roles.
One EA must use:
Account Mode: Transmitter
and the receiving EA must use:
Account Mode: Receiver
3. Check the Transmitter account number.
Make sure the correct account number is entered in the Receiver:
Transmitter Account Number
4. Check Algo Trading.
Algo Trading must be enabled so the Receiver can perform the required trading operations.
5. Check the Receiver login.
The Receiver must be logged in with its normal trading password, not an investor/read-only password.
6. Check the symbol names.
Compare the exact Transmitter and Receiver symbols. If they use different suffixes or substantially different names, configure the appropriate suffix or Special Symbol settings.
7. Check the selected lot-sizing method.
If you are using a risk-based lot-sizing method that requires a Stop Loss for its calculation, make sure the necessary Stop Loss is available.
8. Restart both MT5 terminals.
If the terminals have been running for a long time or appear unresponsive, restart them and test again.
9. Check the Receiver logs.
Open the Experts and Journal tabs in the Receiver terminal and look for errors or messages explaining why the trade was not copied.
10. Check the VPS or computer.
If MT5 terminals are freezing, responding slowly or losing connectivity, test the same setup locally or on another VPS to determine whether the environment is contributing to the problem.
If the problem continues, remove the EA from both terminals, restart the computer or VPS, attach the EA again and configure the Transmitter and Receiver settings manually. Avoid reusing an old set file until you have confirmed that the basic setup works.
If you contact me for assistance, screenshots of both MT5 terminals with Market Watch visible, the Receiver settings and the Experts/Journal messages can help identify the problem.
MT5 to MT5 Trade Copier Quick Setup Video
Please note: The transmitter account requires only the two highlighted settings from the screenshot below. All other configurations must be made on the receiver account side. Changing additional settings in the transmitter account will not make any difference!
If your Transmitter and Receiver accounts use the same broker, you still need two separate MetaTrader 5 terminal installations so both accounts can remain logged in and running at the same time.
Download the broker's MT5 installer and install the second terminal in a different installation folder.
Use one terminal for the MT5 Transmitter account and the other for the MT5 Receiver account. Both terminals can run on the same Windows computer or Windows VPS.
If one Transmitter trade appears multiple times on the Receiver, check whether Local Trade Copier EA MT5© has accidentally been attached to multiple charts.
For a basic one-to-one setup, attach one instance of Local Trade Copier EA MT5© to one chart in the Transmitter terminal and one instance to one chart in the Receiver terminal.
The EA does not need to be attached separately to every symbol chart. One correctly configured instance can manage the trades covered by that Transmitter/Receiver setup.
Also check that another copier or multiplier EA is not copying the same trades simultaneously.
If copied trades on the Receiver open and then close immediately, first check that only the intended Local Trade Copier EA MT5© instance is managing that Receiver setup.
Make sure another trade copier, multiplier or conflicting EA is not attached to another chart and managing the same trades.
Then check the Receiver terminal's Experts and Journal tabs for messages explaining why the position was closed.
If the Transmitter account has an active MQL5 Signals subscription, MetaTrader may restrict MQL5 trading and trade-history functions that Local Trade Copier EA requires for copying.
As a result, trades originating from an active signal subscription may not be available to the copier in the same way as ordinary manual or EA trades.
See the linked MQL5 discussion below for additional information about this MetaTrader restriction.
https://www.mql5.com/en/forum/473035
If a calculated Receiver lot size unexpectedly becomes 0.01 on a VPS while the same setup calculates correctly on another computer, test the EA on a different VPS or local Windows computer.
In some reported cases, changing the virtual processor or moving the setup to another VPS environment resolved the calculation difference.
Before changing VPS providers completely, you can ask your current provider to move the VPS to another host or virtual processor and test again.
Also confirm that the broker's minimum lot size, lot step and the selected Lot Size Type are compatible with the expected Receiver volume.
Learn more about this issue here: https://www.mql5.com/en/forum/470651
Under suitable system and network conditions, Local Trade Copier EA MT5© can synchronize trading actions between local MT5 terminals very quickly, typically in under 0.5 seconds.
This is copier synchronization time, not broker execution time. The final execution of a copied order also depends on the Receiver broker, network connection, market conditions and available liquidity.
If copying becomes noticeably slower or trades appear to be missed, check the Windows computer or VPS for insufficient CPU/RAM resources, frozen MT5 terminals, unstable connectivity or other processes consuming system resources.
Recommended VPS specifications:
2 Terminals: 2 CPU Cores, 4 GB RAM
3-5 Terminals: 4 CPU Cores, 6 GB RAM
7-8 Terminals: 6 CPU Cores, 12 GB RAM
10-15 Terminals: 8 CPU Cores, 16 GB RAM
30+ Terminals: 16-24 CPU Cores, 48-64 GB RAM
Additional VPS considerations:
Latency: Minimize latency by selecting a VPS close to your broker’s data center.
Disk space: Allocate 50-100 GB SSD for terminal installations and data.
Operating system: Use the latest Windows Server version for smooth compatibility.
Choose a VPS with sufficient real-world CPU performance, RAM and SSD storage for the number of MT5 terminals you intend to run. When possible, locate the VPS close to your brokers' trading servers to reduce network latency.
If MT5 charts freeze or the terminals become unresponsive, increasing advertised VPS specifications alone may not solve the problem. Test actual CPU performance and resource usage and, when possible, compare the setup on another Windows computer or VPS.
For high-performance VPS options, visit: https://contabo.com/en/vps/
By ensuring these conditions, you can achieve smooth and delay-free copying.
This video walks you through a basic configuration for copying trades from one transmitter account to one receiver account, assuming neither account has suffixes in their symbols. For example, '.r' in EURUSD.r is a symbol suffix.
This video demonstrates a one-to-one setup where the Transmitter uses a .r suffix and the Receiver uses the base symbol name.
Example:
EURUSD.r → EURUSD
In the Receiver settings, enter:
Suffix of the Transmitter Account: .r
This video demonstrates a one-to-one setup where the Transmitter uses a + suffix.
Example:
EURUSD+ → EURUSD
In the Receiver settings, enter:
Suffix of the Transmitter Account: +
This video demonstrates a setup where the Receiver broker adds a suffix to its symbols.
Example:
EURUSD → EURUSD.r
In the Receiver settings, enter:
Suffix of the Receiver Account: .r
If both the Transmitter and Receiver use the same suffix:
EURUSDm → EURUSDm
enter both settings on the Receiver:
Suffix of the Transmitter Account: m
Suffix of the Receiver Account: m
If both the Transmitter and Receiver use the same suffix:
EURUSDm → EURUSDm
enter both settings on the Receiver:
Suffix of the Transmitter Account: m
Suffix of the Receiver Account: m
When one MT5 Transmitter copies to multiple Receiver accounts, configure the required symbol settings independently on each Receiver.
If the Transmitter uses a suffix, enter the corresponding Suffix of the Transmitter Account setting on each Receiver that requires it.
Each Receiver can also have its own Receiver suffix or Special Symbol mappings when its broker uses different instrument names.
This video demonstrates one MT5 Transmitter copying to two Receiver accounts where one Receiver uses different symbol names.
Configure each Receiver independently. If one Receiver uses a suffix such as .r, enter:
Suffix of the Receiver Account: .r
on that Receiver only.
This video demonstrates two MT5 Transmitter accounts copying to one Receiver.
When a Transmitter uses a symbol suffix, configure the appropriate Suffix of the Transmitter Account setting for the corresponding copying setup on the Receiver.
Always compare the exact symbol names used by each Transmitter with those available on the Receiver broker.
This video demonstrates two MT5 Transmitter accounts copying to one Receiver.
When the Receiver uses a symbol suffix, configure the appropriate Suffix of the Receiver Account setting for the corresponding copying setup on the Receiver.
Always compare the exact symbol names used by each Transmitter with those available on the Receiver broker.
This video showcases a simple trade copying configuration with two transmitter accounts sending trades to two receiver accounts.
An MT5 Receiver cannot copy trades while logged in with an investor/read-only password because that login does not provide trading permission.
Log in to the Receiver account using its normal trading password, confirm that Algo Trading is enabled again, and repeat your test.
A Transmitter may be monitored using read-only access where appropriate, but the Receiver must have permission to trade.
If the EA is configured correctly but trades still cannot be copied, check whether the trading account or broker places restrictions on Expert Advisors, algorithmic trading or particular trading operations.
Check the Receiver's Experts and Journal tabs for relevant messages and confirm the account's trading permissions with the broker.
If you are using a prop-firm, evaluation or funded account, also verify the firm's current rules regarding Expert Advisors, trade copying and account management.
An intermediate MT5 account can act as both a Receiver and a Transmitter in a copying chain.
Example:
MT5 Account 1 → MT5 Account 2 → MT5 Account 3
Account 2 receives trades from Account 1 and also transmits trading activity to Account 3.
This configuration requires separate Local Trade Copier EA MT5© instances for the Receiver and Transmitter roles on the intermediate terminal. Configure each instance carefully for its specific role to avoid unintended copying behavior.
This example shows one MT5 Transmitter copying US index trades to two Receiver accounts with different broker symbol names.
If the Transmitter symbols are US500 and US30 and one Receiver uses symbols such as US500.r and US30.r, configure the Receiver suffix accordingly:
Suffix of the Receiver Account: .r
If another Receiver broker uses substantially different symbol names such as:
US500 → SPX500
or
US30 → WS30
configure the corresponding Special Symbol mappings on that Receiver:
Special Symbol 1: US500,SPX500
Special Symbol 2: US30,WS30
When stock symbols differ between MT5 brokers, compare the exact instrument names available on the Transmitter and Receiver.
If the difference is a suffix, configure the appropriate Transmitter or Receiver suffix setting.
If the brokers use substantially different stock symbol names, use the Special Symbol settings to map the corresponding instruments.
For example, if the Transmitter uses ABBV.NYSE and the Receiver uses ABBVIE, configure the appropriate Special Symbol mapping before copying the trade.
Special Symbol 1: ABBV.NYSE,ABBVIE
In this video, learn how to prevent trades with specific magic numbers from being copied from the transmitter account to the receiver account. These trades might come from an EA or other trading tools with unique magic numbers. To identify the magic number, hover over the ticket number in the Trade or Trading History tab (Expert ID) of the transmitter account. Initially, trades from the Manual Trade Panel EA MT4 are copied. After the expert’s magic number is added to the Magic Numbers Not to Copy setting, further trades are excluded from the receiver account.
In this video, you’ll see how to prevent specific symbols from being copied to the receiver account. A trade is initially copied normally, but after the symbol is added to the Symbols Not to Copy setting, it stops being transferred.
Customize trade multipliers for specific symbols on the receiver account by using this feature.
Custom Symbol Multipliers: This setting allows different multipliers for various symbols, overriding the universal multiplier applied in the receiver settings. If for example a 1 multiplier has been set and in this setting you put: EURUSD2,GBPUSD3.5,USDJPY4 the EURUSD receiver copied trades will be copied with a 2 multiplier, the GBPUSD trades with a 3.5 multiplier and the USDJPY trades with a 4 multiplier, while all other symbols trades will be copied with 1 multiplier. This setting works only when Multiplier or Proportional Multiplier are selected on the Lot Size Type setting above. Also note that any suffixes the receiver account has on its symbols must be included. If for example the receiver account has a .r suffix in its symbols, this setting should be set as: EURUSD.r2,GBPUSD.r3.5,USDJPY.r4
If you are moving an existing MT5-to-MT5 setup to another Windows computer or VPS, you can preserve the Receiver's stored Local Trade Copier configuration data.
1. Close the relevant MetaTrader 5 terminals.
2. In the original MT5 Receiver terminal, go to:
File → Open Data Folder → Bases
3. Locate the gvariables.dat file and make a backup copy.
4. Install the required MT5 terminals on the new Windows computer or VPS.
5. Install Local Trade Copier EA MT5© through your MQL5 account in each new terminal.
6. In the new Receiver terminal, go to:
File → Open Data Folder → Bases
7. With MetaTrader closed, replace the corresponding gvariables.dat file with your backed-up copy.
8. Reopen MetaTrader 5 and carefully verify the Transmitter/Receiver configuration and all open trades before resuming normal copying.
Always keep a backup of the original file until you have confirmed that the transferred setup works correctly.
Trades with lot sizes like 0.001 or even smaller on Deriv Volatility Indexes require updating four critical settings to 0.0001. Refer to the set file provided here for guidance.
The "error of setting timer" appears when the Local Trade Copier EA MT4© cannot initialize on your MT4 chart and is automatically removed. This is a problem within the MT4 terminal and is not caused by the Local Trade Copier EA MT4©. Restart the MT4 terminal and attach the EA again to resolve the issue. If it persists, reboot your computer or VPS, open the MT4 terminal, and reapply the EA.
If Trade is disabled appears in the Receiver's Experts or Journal logs, check:
1. Trading permission: Confirm that the Receiver account is allowed to trade and is logged in with its normal trading password.
2. Algo Trading: Make sure Algo Trading is enabled.
3. Symbol name: Confirm that the Receiver broker provides the corresponding symbol and check whether it uses a suffix.
For example, if the Receiver symbol is:
EURUSD.r
configure:
Suffix of the Receiver Account: .r
If the account itself has trading restrictions, contact the broker or account provider.
If an Unknown Error appears in the Receiver's Experts or Journal logs, restart MetaTrader 5 and test the setup again.
If the error remains, restart the Windows computer or VPS and reattach Local Trade Copier EA MT5©.
Also verify the Receiver account's trading permissions and check whether the broker or account provider restricts Expert Advisors or algorithmic trading.
If the problem continues, save the relevant Experts and Journal messages and contact support for further investigation.
If initialization failed with code 0 appears after a MetaTrader or Windows change, first verify that Local Trade Copier EA MT5© is correctly installed through your MQL5 account.
Go to:
Tools → Options → Community
and log in using the MQL5 account that owns the product.
Then open:
Navigator → Market → Purchases
and reinstall Local Trade Copier EA MT5© if required.
Restart MetaTrader 5 and attach the EA again.
1. Check your internet connection.
2. Restart MetaTrader 5.
3. Make sure MetaTrader 5 is updated.
4. Check whether your firewall or antivirus is preventing MetaTrader 5 from connecting to MQL5 Market.
5. Retry the download. If the problem appears temporary, wait and try again later.
1. Confirm that your internet connection is stable.
2. Close and restart MetaTrader 5.
3. Check whether your firewall or security software is blocking MetaTrader 5 or its connection to MQL5 Market. Configure the appropriate permission or exception if necessary.
4. If the problem persists, reinstall the broker's current MetaTrader 5 terminal after backing up any files or settings you need to preserve.
Error 500 can indicate a temporary server-side or connectivity problem while accessing MQL5 Market.
Check your internet connection, restart MetaTrader 5 and try again.
If MQL5 Market itself is temporarily unavailable, wait and retry the installation later.
Also make sure you are using a current MetaTrader 5 build and that your firewall or security software is not blocking its connection.
Make sure you are logged in to the MQL5 account that owns Local Trade Copier EA MT5©:
Tools → Options → Community
Install the EA through:
Navigator → Market → Purchases
Do not copy the purchased EX5 file from another terminal.
Restart MetaTrader 5 and attach the EA again.
If the problem continues, install a fresh copy of the MetaTrader 5 terminal provided by your broker, log in to your MQL5 account and reinstall the EA through MQL5 Market.
Try the MT5 Trade Copier Free Demo
Test Local Trade Copier EA MT5© between two or more MetaTrader 5 demo accounts before purchasing. The free demo is fully functional for up to 4 hours at a time on demo accounts only.
For download links, installation instructions and the demo reset procedure, visit the Free MT5 Trade Copier Demo page.
If your problem is not covered in this troubleshooting guide, please contact me and include as much information about your setup as possible.
Screenshots of the Transmitter and Receiver terminals, the Receiver settings and relevant Experts/Journal messages can help identify the issue more quickly.