← Înapoi la ghidul de utilizare
Recovery
When your agent goes offline — recovery guide
While an agent is offline, its strategies are paused. Follow the steps below to bring it back or move to a new server. Exchange keys are not on our servers, so a new server needs them entered again.
First — is the server still running?
Check in your cloud console (or on your PC) that the server is on. If it is off, start it; if it is on, restart it. If the agent reconnects in Agents within a few minutes, you do not need the steps below.
Why did it stop?
- AWS Lightsail — stops if a payment failed, or if the server was stopped or deleted in the console. Check the instance state and billing notices in the console.
- Oracle free tier (Always Free) — Oracle states it may reclaim free instances with low utilization (Oracle policy). Whether our agent falls under that rule has not been verified yet. Check in the console whether the instance still exists.
- PC — sleep, reboot, updates, power off or lost internet. It usually reconnects by itself when the PC is back on.
Move to a new server
- Install the agent on a new server — add a new agent in Agents (for a server, see the server setup guide).
- Pair the new agent — check that the fingerprint on screen matches the one the agent shows.
- If you turned on backups, restore the old agent's backup from the new agent's [Backup] tab. Runs move to the new agent, and the old agent stops placing orders even if it comes back.
- Without a backup, remove the old agent, then move its stopped runs to the new agent from the stopped-runs list.
- Enter your exchange keys again (below).
Exchange keys
Keys are non-custodial: our servers hold no copy, and backups do not include them. Enter them again on the new server. If you use an IP allowlist at the exchange, change it to the new server's IP. If the old server may be in someone else's hands, delete the old key at the exchange and issue a new one.
What happened while it was offline
- Strategies were paused — no orders were placed from new signals.
- Orders and positions you had at the exchange are still there (the exchange does not cancel them when the agent stops). They may have filled in the meantime, so check the exchange app first.
- After restoring a backup, [Reconcile] on the wallet screen shows differences from the exchange as 'unknown'. Automatically re-syncing those differences is not available yet.
- Price history (candles) is public data, so the new agent collects it again. Older ranges can take a while.
Alte ghiduri
Creare server ↗Ghid cu capturi de ecran pentru crearea în 5–10 minute a serverului (VPS) pe care rulează strategiile — 10 limbiDB externă SupabaseCreați un Postgres gratuit și conectați-l cu un cont doar pentru citireAdăugare date publiceÎncărcați în propria DB date gratuite precum frică-lăcomie, hashrate sau dobânzi și folosiți-le în strategiiTrezire în timp real cu RedisStrategia reacționează în momentul în care intră o valoare nouă — de la instalare proprie și mai multe servere până la servicii gestionate gratuitePrimii pași în forex (MT5)Backtest cu contul MT5 al brokerului dumneavoastră și rulare paper → demo → cont realÎnregistrarea dispozitivelor pentru protecția coduluiCum stabiliți și verificați dispozitivele care pot deschide codul strategiilor salvate protejatWhen your agent goes offlineMove to a new server and reconnect keys and runs after the server stops or is reclaimedAPI WebSocket P2P (în engleză) ↗Conectați-vă botul sau scriptul la daemonul P2P pentru a primi alertele WATCH TOGETHER confirmate — clienți JavaScript · Python
Documentația completă este aici — Ghid