Account 81233 is reconnecting
Socket closed by broker, retry 3 of 10 — this is a broker-side condition, not a platform one. Restarting the terminal reconnects it; it does not fix a rejected password, and support cannot replace one.
host-09 is not answering its control API
Restart and move will not complete for this account until it does. Its trades are unaffected — the trade connection is a separate one — so this is a reason to wait rather than a reason to escalate.
Account 81233
Exness · DHM
- Login
- 81233
- Broker
- Exness · Exness-Real12
- Platform
- MT5
- Role
- Slave
- State
- Reconnecting
- Last error
- Socket closed by broker, retry 3 of 10
- Host
- host-09 · ap-south-1
- Terminal VM
- 41019
- Owner
- Adam Voss (DHM-40112)
What you can do from here
Three directly, one by asking
Two of these reconnect things and one converges state. None of them can lose money, which is the whole test for whether support does it directly.
There is no password on this page, and no page that has one
Support has no credential surface at all — not write-only, absent. There is no field for account 81233, no page holding one, and /api/support/* contains no credential route, so this is not a permission that could be granted by mistake. If a client needs their password replaced they do it themselves on their own panel, or their tenant admin does it on theirs.
No fieldNo routeCannot be granted
What has to be asked for
Five things, and why each one
Everything below exists on this platform and not on this panel. Each one is a request an admin decides, and the reason is beside it — a panel that simply lacks a button teaches nobody why.
- Wallet credit or refundMoves money. Two people, always — and the goodwill credit below is the only exception.
- Close all positions on an accountRealises somebody’s P&L irreversibly.
- Resume copying after a risk-limit tripThe limit tripped for a reason.
- Disable or re-enable an accountAffects a paying relationship.
- Anything touching product scope, pricing or statusCommercial, not support.