Will My EA Keep Running on MQL5 VPS After Changing Master Password?

 

Hi everyone,

I’m currently running the same trading account on 2 different VPS instances. On one of them, I only want to monitor the account without allowing any trades to be executed. Because of this, I’m considering changing my master password.

But I have some doubts:

  • On my MQL5 VPS, I already have open trades and an EA running.

  • If I change the master password, will the VPS session be closed?

  • Will the EA continue to run and manage trades on the VPS after the password change?

I’d really appreciate insights from anyone who has experience with this situation.

Thanks in advance.

 
Huseyin Furkan Ozturk:

Changing the master password will not close your MQL5 VPS session and your EA will keep running and managing trades as usual.

You will only need the new password if you stop and resynchronize the VPS. For monitoring on another server it is better to use the investor password in read only mode.

 
MQL5 VPS: Changing the master password won’t affect anything. Your EA and trades will keep running.

Personal Windows VPS: If you change the master password, the terminal will disconnect and you’ll need to log in again with the new one.

Changing password via broker’s website (profile): All terminals will require the new password after reconnection.

Creating an Investor password inside MetaTrader: The master password remains unchanged. You simply get a read-only login you can use on another device for monitoring only.

If you just want to monitor without trading, the best option is to use the Investor password.
 
@Miguel Angel Vico Alba #Changing the master password will not close your MQL5 VPS session and your EA will keep running and managing trades as usual.
@Farzad Saadatinia #MQL5 VPS: Changing the master password won’t affect anything. Your EA and trades will keep running.

The fact that changing the master password has no effect on MetaQuotes Virtual Hosting service, is for me a very concerning security risk.

This is in no way my case, but imagine a situation where a 3rd party is trading recklessly on one's account. One would expect that changing the master password would regain control to block intervention by the 3rd party. However, according to what has been stated above, this would not block the 3rd party influence. I find that very concerning.

 
Fernando Carreiro #:

The fact that changing the master password has no effect on MetaQuotes Virtual Hosting service, is for me a very concerning security risk.

This is in no way my case, but imagine a situation where a 3rd party is trading recklessly on one's account. One would expect that changing the master password would regain control to block intervention by the 3rd party. However, according to what has been stated above, this would not block the 3rd party influence. I find that very concerning.

The fact that changing the master password does not affect an active MQL5 VPS session can be seen in two ways:

  • On the one hand, for most users this is an advantage, because it prioritizes operational continuity. Their EAs keep running without interruption even if the password is changed, which prevents issues with strategies that cannot be stopped abruptly.
  • On the other hand, as you mention, from a security and control perspective it removes the ability to use the password change as an "emergency cut-off" to invalidate access. In that sense, it could indeed be a risk if someone unauthorized is already running operations.

It seems the design favors convenience for the majority, but it would certainly make sense to offer an option for those who prioritize security; for example, letting the user choose whether changing the master password should keep sessions active or force all connections to be invalidated.