Will My EA Keep Running on MQL5 VPS After Changing Master Password?
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.
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 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.
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.
With the latest issue with MetaQuotes VPS service being inaccessible of users being unable to stop their VPS or their EAs still trading, here is a prime example of the security risk concern I had.
With the VPS access cut off, they are not even able to halt the account access by changing the master password.
So, I will repeat my concern—it is a significant security risk and a major design flaw!
- 2025.09.03
- www.mql5.com
This design has two sides. On the one hand, it guarantees uninterrupted trading even if the master password is changed. On the other hand, it removes the possibility of using a password change as an emergency stop.
It would make sense if MetaQuotes allowed users to choose whether a password change should keep sessions active or force all connections to be terminated.
Regarding the current issue with MQL VPS: according to a user, the VPS can still be stopped manually, so even if limited, there is some form of emergency mechanism.
Forum on trading, automated trading systems and testing trading strategies
Amin Abazari, 2025.09.03 22:20
go to the following link and stop the vps.
In any case, I agree that a password change should terminate all active sessions, or at least offer a checkbox option so users can decide between continuity and forced disconnection.
Update: It seems that the option to stop the VPS from the previously provided link is not working.Forum on trading, automated trading systems and testing trading strategies
Kareem Aljamal, 2025.09.03 23:40
change the account to a demo account it will stop from the current real one
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
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.