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

# troubleshooting

> Solutions to common Botify issues and error messages.

<AccordionGroup>
  <Accordion title="Cookie expired / Invalid cookie">
    **Symptom:** Account shows red status dot, Failed filter chip shows it, or you see a cookie validation error on add.

    **Fix:**

    1. Go to the **Cookies** tab → click **Refresh** on the affected account
    2. If refresh fails (account fully invalidated), go to **Accounts** tab → right-click → **Browser Login** to re-authenticate
    3. For bulk expired cookies, use **Accounts → Remove Expired** to clean up and re-add via Batch Import

    <Note>
      Roblox cookies expire after \~30 days of inactivity or when the account logs out. Enable **Auto Cookie Refresh** (Settings → Cookie Management) to prevent this.
    </Note>
  </Accordion>

  <Accordion title="MongoDB connection failed">
    **Symptom:** Botify shows a connection error on startup or account data doesn't load/save.

    **Fix:**

    1. Check your internet connection
    2. Disable any VPN — some VPNs block MongoDB Atlas endpoints
    3. Check Windows Firewall — ensure Botify.exe is allowed outbound on ports **27017** and **443**
    4. If behind a corporate/school network, MongoDB Atlas connections may be blocked entirely — use a personal network or hotspot
    5. Restart Botify

    <Warning>
      MongoDB connection uses built-in credentials. Do not attempt to change them — Botify manages this automatically.
    </Warning>
  </Accordion>

  <Accordion title="Multi-Roblox not working / Only one instance launches">
    **Symptom:** Second Roblox instance doesn't open, or an existing one takes focus instead.

    **Fix:**

    1. **Run Botify as Administrator** — right-click → Run as administrator. Multi-Roblox mutex bypass requires admin privileges.
    2. Check **Settings → General → Multi-Roblox** is enabled
    3. If Roblox was already open before Botify launched, close all Roblox instances and let Botify manage them
    4. Ensure you're not running another mutex-bypass tool (Bloxstrap, etc.) that conflicts

    <Note>
      Botify initializes the mutex bypass on startup. If admin elevation was declined, restart with the UAC prompt accepted.
    </Note>
  </Accordion>

  <Accordion title="High RAM usage / System running out of memory">
    **Symptom:** PC slows down, RAM is maxed, or Botify shows memory warnings.

    **Fix:**

    1. Enable **Settings → Memory & CPU Optimizer → Process Optimizer (Master)**
    2. Enable **Working Set Trim** and set **Trim Only in Game** to `true`
    3. Enable **Kill Crash Handlers**
    4. Enable **Ultra-Low GPU Mode** for 15+ instances
    5. Reduce **Max Concurrent** in Settings → Launch Tuning
    6. Lower **Memory Warning %** threshold to get earlier alerts (default: 85%)

    <Tip>
      See the [Process Optimizer](/process-optimizer) page for expected RAM usage per instance with each setting combination.
    </Tip>
  </Accordion>

  <Accordion title="Bots not joining the server">
    **Symptom:** Roblox opens but accounts end up in a different game, or the In/Out column stays "Out".

    **Fix:**

    1. Verify your **ERLC Server Code** in Settings — it should be the exact private server code (e.g., `UTAHUSA`)
    2. Verify your **PRC API Key** is correct and has not been rotated
    3. Ensure the private server is online and accessible
    4. Check the Logs tab for teleport error codes (524, 773, 279)
    5. Try manually launching one account via right-click → **Launch ERLC** to test

    <Note>
      Server code is case-sensitive. Double-check capitalization if bots launch but join the wrong server.
    </Note>
  </Accordion>

  <Accordion title="Ghost server detected — bots keep relaunching">
    **Symptom:** Botify logs show "Ghost server detected", all bots are killed, and the cycle repeats.

    **What's happening:** Botify tracked 20+ bots but the PRC API reports fewer than 10 players visible — indicating a Roblox server glitch where players exist but are invisible to the API.

    **Fix:**

    1. Wait — the 300-second ghost reset cooldown prevents rapid loops
    2. If it persists, your private server may be experiencing a Roblox-side ghost glitch. Rejoin with your main account to check
    3. Reduce `deploy_threshold` in Settings → Server Thresholds to deploy fewer bots
    4. If the server code changed, update it in Settings → Connection & API

    <Info>
      Ghost detection thresholds: **20+ tracked bots** AND **fewer than 10 PRC players** = ghost server trigger.
    </Info>
  </Accordion>

  <Accordion title="Stale join alert keeps appearing">
    **Symptom:** Dialog pops up saying accounts are running but not in the server.

    **What's happening:** The [Stale Join Watchdog](/watchdog) detected accounts that launched but didn't appear in the PRC player list within the timeout window.

    **Fix:**

    1. Increase **Stale Join Timeout** (Settings → General) if accounts take longer to load on your connection
    2. Check those accounts' cookies — refresh if yellow/red
    3. Enable Auto-Relaunch to handle stale accounts automatically
    4. If the alert fires immediately, verify your PRC API Key is returning correct player data

    See the [Watchdog](/watchdog) page for full configuration details.
  </Accordion>

  <Accordion title="Anti-AFK not working / accounts getting kicked">
    **Symptom:** Accounts are being kicked from ERLC for inactivity despite Anti-AFK being enabled.

    **Fix:**

    1. Ensure Anti-AFK is enabled on the **Automation** tab
    2. Reduce the **Interval** — try 6 or 9 minutes instead of 15
    3. Try a different **Action Type** — some ERLC servers specifically check for jump inputs vs. camera movement
    4. If **User-Safe Mode** is on, it may be deferring cycles too long — try disabling it
    5. Check that Roblox windows haven't crashed (check Logs for crash entries)
  </Accordion>

  <Accordion title="Discord OAuth2 login fails / 'Client role not found'">
    **Symptom:** OAuth2 flow completes but Botify rejects login with a role error.

    **Fix:**

    1. Ensure you are a member of the **Botify Discord server**
    2. Verify you have the **"Client"** role — contact Botify support if you purchased but don't have it
    3. Try logging out of Discord in the browser and re-authenticating
    4. If using a VPN, disable it — Discord OAuth can redirect incorrectly through some VPNs

    <Warning>
      The "Client" role is required. Without it, Botify will refuse login regardless of payment status.
    </Warning>
  </Accordion>

  <Accordion title="Botify won't start / crashes immediately">
    **Symptom:** EXE opens and closes instantly, or shows a Python error.

    **Fix:**

    1. **Run as Administrator** — most startup crashes are caused by insufficient privileges
    2. Check Windows Defender / antivirus — add Botify.exe as an exclusion (false positives are common with PyInstaller EXEs)
    3. Ensure you're on **Windows 10 or 11** — other OS versions are not supported
    4. Delete `account_store.json` in the same folder as the EXE if it's corrupted, then relaunch
    5. Check the `persistence_log.txt` file next to the EXE for error details
  </Accordion>
</AccordionGroup>

***

## Still Need Help?

Join the **Botify Discord server** and open a support ticket. Include:

* Your Botify version (shown in the title bar)
* A copy of `persistence_log.txt`
* A description of what you were doing when the issue occurred