Run and monitor EAs on a VPS

Prepare the exact environment

Save full inputs, symbol names, timeframes and the current position/order state. Check account connection and required dependencies. Distinguish MetaTrader virtual hosting from a general Windows VPS: their migration and permission behavior differ. Do not assume a backup of local files alone recreates the active trading environment.

Verify the migration and execution location

For MetaTrader virtual hosting, check the migrated environment and virtual journals. Its automated-trading permission differs from the local switch; treat synchronization as an operational change. Avoid running the same strategy instance from multiple terminals on the same account without an explicitly tested coordination design. On a general VPS, verify the actual terminal process and trading permissions after reconnecting.

Inspect operation without forcing a trade

Check connection status, history readiness, journal errors, actual positions and stop protection. No new trade may simply mean no qualifying signal; it is not alone proof of a fault. After an update or restart, inspect whether the EA recognizes existing orders and avoids duplicates. Keep an incident record and verify the tested method for preventing new entries without accidentally abandoning existing position management.

Checks to make before deciding

• Describe the broad entry idea, exit mechanism and intended market conditions. Keep an internal precise specification even if the public explanation omits implementation details.
• Check indicator shifts, buffer readiness and bar closing times. Confirm that an entry uses information available at that moment, not the completed value of a future bar.
• Test repainting and revised external data. Preserve what was known at signal time and compare it with later values; a clean historical plot alone is insufficient evidence.
• Inspect whether positions are added by distance, loss recovery or exposure scaling. Support no-grid and no-martingale claims with all relevant code paths, including shared components.
• Compile the final sale source without errors and review warnings. Archive the exact compiler output and compare binary checksums with the version used in final testing.
• Test netting and hedging only where claimed as supported. Examine opposite orders, partial fills, reversals and magic-number attribution under each relevant account model.
• Restart with open positions and pending orders. Verify state recovery, no duplicate entry, correctly restored stops and safe handling of missing history or indicators.
• Simulate connection loss, market closure and rejected trade requests. Check return codes and bounded retries; do not treat submission as confirmed execution.