Exness Password Change: What Drops and What Survives (Namibia)
Two separate passwords guard an account, and each of them cuts a different set of connections when it is changed. This page maps which of them drop, which survive untouched, and the order that avoids losing both sides at once.
Open Exness Account →A password change is not one event but two, because two separate passwords guard an account and each cuts a different set of connections. Changing the Personal Area password ends the portal sessions — the browser on a second device, the phone that was already signed in — while leaving every terminal connection alive. Changing the trading-platform password does the reverse: the portal is untouched and every terminal copy loses its account, including the one on a second machine that nobody is looking at. Positions, pending orders, balances and account numbers survive both. The safe order is portal first, confirmed sign-in second, trading password third.
The order that keeps one side reachable
The risk in a password change is not the change itself but the gap between the two of them, when neither side is confirmed. The sequence below keeps a confirmed way in at every step.
- Start from a device that is already signed in, and keep that session open until the change is finished.
- Change the Personal Area password first: it is the side that can be recovered by email if the change goes wrong.
- Sign in again on that primary device before touching anything else, so at least one confirmed way in exists.
- Change the trading-platform password second, then reconnect the terminal that carries open positions before any secondary copy.
- Walk the rest of the list deliberately: the second machine, the phone, and anything left running on a chart.
What a password change does not touch
A change on one side never resets the other, because the Personal Area password and the trading-platform password are set separately. That separation is what makes a half-finished change dangerous: the portal can be open while every terminal is blind, or every terminal can be live while the portal locks you out.
Nothing on the account itself moves. Positions already open stay open on the server, pending orders keep their levels, account numbers and balances are unchanged, and the email on file is untouched. A password decides the way in, not what is behind the door.
Why the two sides fail separately
The two passwords are independent by design, and a reset on one leaves the other exactly as it was. That independence is convenient right up to the moment a change is half-finished, because it means there is no single state called signed out. There is a state where the portal answers and no terminal does, and a state where every terminal trades and the portal refuses you.
Both states are recoverable, and neither is comfortable while a position is open. The map is worth having in advance for one reason: the side that fails is decided by which password you touched, not by which device you touched it from.
The connection nobody notices
The connections that cause trouble are the ones left running out of sight. A terminal copy on a second machine, a phone in a drawer, a chart left open on a machine at home — none of them announce that they have been cut. They simply stop being the thing you assumed was watching.
The rule of thumb is to enumerate before changing rather than after. Write down every place the account is currently connected from, and treat the list as the checklist for the hour after the change. A connection that is not on the list is a connection you will discover at the worst possible moment.
What survives either change
Nothing behind the door moves. Open positions stay open on the server and keep running to their stops and targets whether or not any terminal is watching them. Pending orders keep their levels. Balances, account numbers and the email on file are unchanged.
This is the reassuring half of the map and the reason a change can be made calmly: the worst outcome of a badly sequenced password change is a period of not being able to look, not a period of not being covered. That is still a real cost with a position open, which is why the sequence exists.
Connection by connection
| Connection | Which password it depends on | What to check after a change |
|---|---|---|
| The portal in a browser | Personal Area password | Sign in again on every browser and device that had it open |
| The mobile app, already signed in | Personal Area password | Expect the session to end; sign in again before relying on it |
| A terminal on the main machine | Trading-platform password | Reconnect the account: the charts stay, the connection does not |
| A terminal copy on a second machine | Trading-platform password | Nothing prompts you there, so check it deliberately |
| A script left running on a chart | Trading-platform password | It stops acting for as long as the account is disconnected |
| Open positions and pending orders | Neither | They sit on the server and are untouched by either change |
| Account numbers and balances | Neither | Unchanged: a password decides the way in, not what is behind it |
The two passwords are set separately, so a change on one side never resets the other.
Frequently asked questions
If one password is changed, does the other change with it?
Which connections stop working after the trading-platform password is changed?
Do open positions close when a password changes?
Why does a terminal on a second machine keep failing after a password change?
In which order should the two passwords be changed?
What is left working if a change goes wrong halfway?
Reviews
What traders say about Exness account access:
Overall Great App. Overall it’s a great App, have some minor issues with login and connectivity sometimes but works like a charm so far
Signing in problem. I logged out of my Exness account and I can’t sign in again and it’s been about a week now please . Kindly please have a look at my account for me please
Poor App. The app sometimes doesn't work in the critical sensitive trading moments, requies login again n again, lags & unresponsive with missing sometimes some data