A stop-loss stored on the broker's server will execute even if the home computer dies, the VPS crashes, or the connection drops. A stop managed by a script running on the client side only exists while the script does.
The distinction is often hidden. Some expert advisors implement trailing stops or breakeven moves by monitoring price and sending a modify order. If the connection fails mid-trade, the last stop on the server is the only protection left, and it might be a long way from where the script had planned to move it.
Virtual stops are even riskier. These are stops that aren't sent to the broker at all. The EA watches price and closes the position when it reaches the level. Some use them to hide stop levels from the broker. The cost is complete dependence on connectivity.
A good compromise: place a real stop on the server that's wider than the intended one, as a disaster net. The script manages the tighter exit. If the script fails, the wide stop catches the trade.
Many blown accounts began with the sentence "the EA was supposed to close it."
Are virtual stops used here at all, and has one ever failed at the worst time?
Server-side stops beat client-side stops, and it's not close
-
Shadow Trader
- Posts: 5594
- Joined: Wed Sep 09, 2026 5:19 pm
-
FXS Prop Desk
- Posts: 1691
- Joined: Wed Oct 07, 2026 9:52 am
Re: Server-side stops beat client-side stops, and it's not close
The hidden part is the worst of it: an EA can show a "stop" on screen that's really a virtual line. Checking the order's SL field in the trade tab, not the chart, tells whether the broker actually holds it. For prop accounts, a missing server stop during a disconnect can breach the daily loss rule.
FXS Official Team | The Idea Lab & Strategy
-
Amanhasnoname
- Posts: 2060
- Joined: Fri Oct 30, 2026 9:45 am
Re: Server-side stops beat client-side stops, and it's not close
I used virtual stops for a few months on a small grid EA I was testing, mostly because a forum post convinced me the broker was hunting my stops. It worked fine until the day my VPS provider did a scheduled reboot that I'd missed in their email. The terminal came back up, but the EA needed a manual restart and I was at work. Four open positions sat with no protection for most of an afternoon, and one of them ran about sixty pips past where the virtual stop should have closed it.
After that I went to exactly the setup you describe. Every order goes out with a real server stop, usually about one and a half times the distance of the stop the EA manages, and the EA tightens from there. If anything breaks, the worst case is known before I enter.
The other habit I picked up is checking the order list from my phone app once a day. If a position shows no stop in the broker's own app, something is wrong, whatever the chart on the VPS says.
After that I went to exactly the setup you describe. Every order goes out with a real server stop, usually about one and a half times the distance of the stop the EA manages, and the EA tightens from there. If anything breaks, the worst case is known before I enter.
The other habit I picked up is checking the order list from my phone app once a day. If a position shows no stop in the broker's own app, something is wrong, whatever the chart on the VPS says.