> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reconnect-tool.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Fixing an Offline or Disconnected Reconnect Device

> Diagnose and fix Reconnect devices showing as Offline or disconnected. Covers WebSocket drops, Android battery kills, and stale last-seen timestamps.

If your device shows as **Offline** in the Reconnect dashboard, the client has lost its connection to the server — but in most cases it only takes a moment to get back online. Work through the issues below that match what you're seeing.

<AccordionGroup>
  <Accordion title="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:**

    1. Stop the Reconnect client — press **Ctrl+C** in Termux, or close the Windows app from the system tray.
    2. Restart the client.
    3. Wait **10–15 seconds**, then check your dashboard — the device should reappear as **Online**.
  </Accordion>

  <Accordion title="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                       |
  </Accordion>

  <Accordion title="&#x22;Last seen&#x22; 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

    **Fix:** Physically access the device and restart the Reconnect client manually. Once the client connects, the dashboard updates immediately.
  </Accordion>

  <Accordion title="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.

    <Steps>
      <Step title="Open Android Settings">
        Open the **Settings** app on your Android device.
      </Step>

      <Step title="Navigate to Termux battery settings">
        Go to **Apps**, find and tap **Termux**, then tap **Battery**.
      </Step>

      <Step title="Set to Unrestricted">
        Select **Unrestricted** (or **Don't optimize**, depending on your Android version).
      </Step>
    </Steps>

    <Note>
      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
    </Note>
  </Accordion>

  <Accordion title="Device is Online but not rejoining">
    **Cause:** The rejoin loop may be paused, or the device card may show an incomplete account setup.

    **Fix:**

    1. 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.
    2. Open the **Device Control Panel** for that device and send a **Sync** command to push the latest state to the client.
    3. If the loop remains paused after syncing, send a **Restart** command to force the client to reload.
  </Accordion>
</AccordionGroup>

<Tip>
  If your device keeps going offline repeatedly, battery optimization is almost always the culprit on Android. Make sure you've followed the full disable steps in the accordion above before investigating further.
</Tip>