You can check VPS logs/journal (right click on your VPS in MT4 Navigator window and select Journal) and check those positions.
Because it seems you were traded on same trading account which you used for subscription.

- www.mql5.com
Some of VPS services that I use, stopped connecting to trading servers. VPS logs attached.
And some other VPS services now misread opened positions on the trading account, it looks like this:
2020.12.14 23:03:18.430 '500041376': Signal - local position [#1607730724 buy 0.00 Tr3Ü at 0 sl: 1], does not correspond to signal provider
2020.12.14 23:03:18.430 '500041376': Signal - local position [#1607730725 buy 0.00 Tr3Ü at 0 sl: 1], does not correspond to signal provider
2020.12.14 23:03:18.430 '500041376': Signal - local position [#1607730725 buy 0.00 Tr3Ü at 0 sl: 1], does not correspond to signal provider
2020.12.14 23:03:18.430 '500041376': Signal - local position [#1607904919 buy 0.00 1¶ä ñ? at 0 sl: 1], does not correspond to signal provider
2020.12.14 23:03:18.430 '500041376': Signal - local position [#1607904919 buy 0.00 1¶ä ñ? at 0 sl: 1], does not correspond to signal provider
2020.12.14 23:03:18.430 '500041376': Signal - local position [#1607904920 buy 0.00 1¶ä ñ? at 0 sl: 1], does not correspond to signal provider
And of course it's causing a lot of troubles...
Your connection to your trade server seems OK, but a strange instrument is not copied to your account.
Probably that instrument is not mapped correctly on your trading account.
Ask the signal provider for help and advice on better broker/server setups for copying the signal.
I did not see anything in your vps log file (nothing about any position opened).
You can check VPS logs/journal (right click on your VPS in MT4 Navigator window and select Journal) and check those positions.
Because it seems you were traded on same trading account which you used for subscription.
Logs that I have attached (vps logs.txt) are from the VPS that can't connect to a trading server and they are not looking ok. The VPS is constantly trying to connect to mt4-demo-dc1.roboforex.com:443 and fails.
Strange BUY positions in question (with 0.00 trading lots) are from another VPS.
Logs that I have attached (vps logs.txt) are from the VPS that can't connect to a trading server and they are not looking ok. The VPS is constantly trying to connect to mt4-demo-dc1.roboforex.com:443 and fails.
Strange BUY positions in question (with 0.00 trading lots) are from another VPS.
Try to move your MQL5 VPS to another server and try again.
https://www.mql5.com/en/vps/subscriptions
Try to move your MQL5 VPS to another server and try again.
https://www.mql5.com/en/vps/subscriptions
That actually helped, thank you.

- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
Some of VPS services that I use, stopped connecting to trading servers. VPS logs attached.
And some other VPS services now misread opened positions on the trading account, it looks like this:
2020.12.14 23:03:18.430 '500041376': Signal - local position [#1607730724 buy 0.00 Tr3Ü at 0 sl: 1], does not correspond to signal provider
2020.12.14 23:03:18.430 '500041376': Signal - local position [#1607730725 buy 0.00 Tr3Ü at 0 sl: 1], does not correspond to signal provider
2020.12.14 23:03:18.430 '500041376': Signal - local position [#1607730725 buy 0.00 Tr3Ü at 0 sl: 1], does not correspond to signal provider
2020.12.14 23:03:18.430 '500041376': Signal - local position [#1607904919 buy 0.00 1¶ä ñ? at 0 sl: 1], does not correspond to signal provider
2020.12.14 23:03:18.430 '500041376': Signal - local position [#1607904919 buy 0.00 1¶ä ñ? at 0 sl: 1], does not correspond to signal provider
2020.12.14 23:03:18.430 '500041376': Signal - local position [#1607904920 buy 0.00 1¶ä ñ? at 0 sl: 1], does not correspond to signal provider
And of course it's causing a lot of troubles...