Device shows Offline but the client is running
Device shows Offline but the client is running
Most common cause: The client lost its WebSocket connection to the Reconnect server without restarting itself.Fix:
- Stop the Reconnect client — press Ctrl+C in Termux, or close the Windows app from the system tray.
- Restart the client.
- Wait 10–15 seconds, then check your dashboard — the device should reappear as Online.
Device went Offline on its own
Device went Offline on its own
Several things can cause a device to drop offline without you doing anything. Use the table below to identify the cause and apply the correct fix.
| Cause | Fix |
|---|---|
| Android killed Termux (battery optimization) | Disable battery optimization for Termux in Android Settings — see the guide below |
| Device lost internet connection | Check Wi-Fi or mobile data on the device |
| Roblox crashed and Reconnect stopped | Restart the Reconnect client and check client logs for errors |
| Reconnect server restart | The client reconnects automatically — wait up to 30 seconds |
"Last seen" shows a long time ago
"Last seen" shows a long time ago
A stale “last seen” timestamp means your device hasn’t checked in with the dashboard for an extended period.Possible reasons:
- The device was turned off or rebooted without Reconnect being restarted afterward
- A network issue prevented the client from reaching the server
- Android killed the Termux process in the background
Disabling battery optimization on Android
Disabling battery optimization on Android
Battery optimization is the number one cause of Termux being killed on Android. Disabling it keeps ReconnectX or Termux running reliably in the background.
On some devices (particularly Huawei, Xiaomi, and OPPO), the setting is located under:Battery → App Launch → set Termux to Manual, then enable all three toggles:
- Auto-launch
- Secondary launch
- Run in background
Device is Online but not rejoining
Device is Online but not rejoining
Cause: The rejoin loop may be paused, or the device card may show an incomplete account setup.Fix:
- Check the account setup badge on your device card in the dashboard. If it shows 0/X, the rejoin loop is likely paused due to a missing configuration.
- Open the Device Control Panel for that device and send a Sync command to push the latest state to the client.
- If the loop remains paused after syncing, send a Restart command to force the client to reload.