4 terminals are on hosts that are not answering
They sit on host-09, host-06. Restart, move and drain are all calls to the agent on the host, so those three buttons will not complete for these rows — the agent has to answer first. Whether they are still copying is a separate question, answered by the host’s state: control and trades are different connections. Fix the host, then the terminal.
2 terminal(s) cannot log in
Both are Invalid account (10004), which means the password at the broker is not the one we hold. Nobody here can read or recover the stored one — the owner has to supply a new one, and until they do this account copies nothing.
Terminals16across 8 hosts
Copying10receiving and placing
In trouble3login failed or reconnecting
Masters5investor password only
Every terminal
Across every tenant and every host
| Login | Role | Tenant | Broker & estate | Host | State | VM | |
|---|---|---|---|---|---|---|---|
| 5021 | Master | — platform | Exness Exness-Real12 MT5 | host-04 | Copying | — | |
| 5044 | Master | — platform | IC Markets ICMarketsSC-Live08 MT5 | host-04 | Copying | — | |
| 5062 | Master | — platform | Pepperstone Pepperstone-Live04 MT5 | host-01 | Connected | — | |
| 5077 | Master | — platform | Exness Exness-Real12 MT5 | host-06 | Login failed Invalid account (10004) — the investor password was replaced 2 days ago | — | |
| 5090 | Master | — platform | Pepperstone Pepperstone-Live04 MT5 | host-01 | Connected | — | |
| 81204 | Slave | DHM | Exness Exness-Real12 MT5 | host-01 | Copying | 41007 | |
| 81219 | Slave | DHM | IC Markets ICMarketsSC-Live08 MT5 | host-01 | Copying | 41012 | |
| 81233 | Slave | DHM | Exness Exness-Real12 MT5 | host-09 | Reconnecting Socket closed by broker, retry 3 of 10 | 41019 | |
| 81247 | Slave | NSC | Pepperstone Pepperstone-Live04 MT5 | host-02 | Copying | 41024 | |
| 81260 | Slave | NSC | Exness Exness-Real12 MT5 | host-07 | Copying | 41031 | |
| 81274 | Slave | MFX | IC Markets ICMarketsSC-MT4-12 MT4 | host-07 | Copying | 41038 | |
| 81288 | Slave | MFX | Exness Exness-Real12 MT5 | host-09 | Login failed Invalid account (10004) — client changed the password at the broker | 41044 | |
| 81301 | Slave | BLH | Pepperstone Pepperstone-Live04 MT5 | host-09 | Copying | 41051 | |
| 81315 | Slave | BLH | Exness Exness-Real12 MT5 | host-11 | Copying | 41058 | |
| 81329 | Slave | CDR | IC Markets ICMarketsSC-Live08 MT5 | host-11 | Stopped Subscription lapsed 3 days ago | 41063 | |
| 81342 | Slave | CDR | Exness Exness-MT4Real8 MT4 | host-12 | Copying | 41070 |
Credentials
The rule, and why this page is where it is stated
- No route in this panel returns a stored password. Including for you. Credentials are write-only through every echoSignals API — there is no reveal control, no export, and no support flow that produces one. Super admin is not an exception; the exception does not exist in the schema.
- Replacing is the only operation. A new password is enveloped under the account’s own data key and dispatched to the host that needs it. Dispatch is audited with the account, the host and the actor — the value is not.
- A master stores only the investor password, role-enforced in the schema, so a leaked master credential cannot trade. A slave stores a trading password because it has to place orders.
- Support has no credential surface at all — absent, not hidden, and not a role flag away. If a support agent tells you they need a password, that is the incident.