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

# Fix Hub accounts: errors, capture problems, license limits

> Fix common Vanguard Hub problems: login failures, disconnects, capture issues, license limits, and wrong feature timing limits.

When a Vanguard Hub account does not behave as expected, the status line on the account card is the first clue. Use the accordion groups below to find your symptom and follow the steps to fix it.

> **No login yet**
>
> The account has no captured login files. It cannot start until you run **Capture login** or re-capture an expired login.
>
> **1. Run Capture login**
>
> Go to the account card and click **Capture login**.
>
> **2. Install Wireshark and Npcap if needed**
>
> The first time you capture, the Hub checks for Wireshark and Npcap. If either is missing, follow the on-screen link to install them, then restart Vanguard Hub.
>
> **3. Start the capture**
>
> The Hub watches your network for the game's login traffic. Log into the game on the same PC while the capture is running. The capture window shows a 10-minute countdown.
>
> **4. Wait for success**
>
> When the Hub sees the login, it saves the files and the account status changes to **Off**, ready to start.
>
> > [!TIP]
> >
> > If you installed Wireshark but the Hub still says Npcap is missing, make sure you installed Npcap (not just Wireshark itself). Npcap may need to be installed with the Wireshark installer or downloaded separately from the Npcap website.

> **Sign-in REFUSED (code N) stopped**
>
> The game server refused the login with an error code. Common causes and fixes:
>
> * **Expired login token:** capture a fresh login. Tokens expire after a time or when the game updates.
> * **Wrong server:** open the account's **Edit** dialog and check the game server host and port. Make sure the server matches the one you log into by hand.
> * **Logged in elsewhere:** if the game is open on your phone or in another client, the server may reject the Hub's login. Close the other session, or wait and let the Hub reconnect with its reconnect setting.
> * **Account suspended or banned:** the code in parentheses is the server reply. If the same code appears on the real game client, the issue is with the account itself.
>
> **1. Recapture login**
>
> Open the account card, click **Capture login**, and log into the game again while the capture runs.
>
> **2. Check the server**
>
> In the **Edit** dialog, verify the game server host and port.
>
> **3. Try Log in only**
>
> Use **Log in only** to test the login without starting the loop. This isolates whether the problem is login or something else.

> **Stopped unexpectedly**
>
> The account process ended without being told to stop. This usually means a crash or a forced shutdown.
>
> * Check the account's **Activity Log** on the full Vanguard page for the last action before the stop.
> * If the last line is a refused reply with a rare error code, Vanguard may have crashed trying to parse it.
> * Make sure Vanguard Hub has enough free RAM and disk space.
> * If the account crashes repeatedly at the same action, open the full Vanguard page and switch that feature off until you can investigate further.
>
> **1. Open the full page**
>
> Click **Open** on the account card to go to the full Vanguard page.
>
> **2. Check the Activity Log**
>
> Look at the **Activity Log** page for the last lines before the stop.
>
> **3. Disable the suspect feature**
>
> If one feature always runs right before the crash, switch it off on its card (**Chores**, **Military**, **Dailies**, or **Gather**) and restart the account.

> **Not answering**
>
> The Hub has not heard from the account process in longer than expected. The process may have frozen or the connection between the Hub and the account broke.
>
> * Press **Stop** on the account card. If that does not work, wait a few seconds and press **Stop** again.
>
> * Once stopped, press **Start** to bring the account back online.
>
> * If this happens often, check that your PC is not going to sleep while the Hub is running.
>
> > [!NOTE]
> >
> > **Not answering** is different from **Disconnected**. Not answering means the account process is still alive but silent; Disconnected means the game server ended the session.

> **Disconnected reconnecting is off**
>
> The game server logged the account out and **reconnecting** is turned off for this account. The Hub will not try to log in again until you press **Start**.
>
> * If you want the Hub to stay online automatically, turn reconnecting on in the account settings.
> * If you turned reconnecting off on purpose so you can play on your phone, this is expected. Press **Start** when you want the Hub to take over again.

> **Disconnected reconnecting in N**
>
> The game server logged the account out and the Hub is waiting N minutes before trying to reconnect. This happens when reconnecting is on and the Hub is respecting the reconnect wait interval.
>
> * If you logged in elsewhere and want the Hub to take over sooner, press **Stop** then **Start** to force an immediate reconnection.
> * If the delay is too long, open the full Vanguard page, go to **Settings**, and reduce the reconnect wait time.

> **Capture problems: Wireshark not installed**
>
> The Hub could not find Wireshark on your PC.
>
> * Install Wireshark from the link in the Hub message.
> * Restart Vanguard Hub after installation.

> **Capture problems: no login seen in 10 minutes**
>
> The capture window ran out of time without spotting the login traffic.
>
> * Make sure you log into the game on the same PC while the capture is active.
> * If your PC has multiple network adapters, the capture may be watching the wrong one; try disabling other adapters temporarily.
> * Close the game completely before starting the capture, then open it and log in fresh.

> **Capture problems: Npcap admin rights**
>
> On some Windows setups, Npcap requires you to run the capture as administrator.
>
> * Restart Vanguard Hub by right-clicking it and choosing **Run as administrator**, then try the capture again.

> **License limit reached**
>
> The Hub tried to start an account, but the license is already running its maximum number of clients.
>
> * Stop one of the currently running accounts to start another.
> * For a key with a higher client limit, click **Open** on any account card, press **Contact us** in its sidebar and pick **Billing & licenses**.

> **Key moved to another copy**
>
> You pasted the same license key into a second copy of Vanguard Hub (or a standalone Vanguard) on another PC.
>
> * The first Hub detected this and logged every account out automatically to stay within the limit.
> * Decide which PC should use the key. Paste the key into only one Hub at a time. If you need both PCs running, you need two separate license keys.

> **A limit looks wrong**
>
> If a feature is waiting too long, acting too often, or skipping when it should run, its timing limits may be set incorrectly.
>
> **1. Open the feature card**
>
> Click **Open** on the account card, then go to the feature page (for example, **Chores**, **Military**, **Dailies**, or **Gather**).
>
> **2. Open Settings**
>
> Click the **Settings ▾** fold on the feature card.
>
> **3. Check the Advanced fold**
>
> Click the **Advanced** fold to see the timing values. Adjust them to match your kingdom's pace.

## Still stuck?

If none of the above fixes the problem, open the full Vanguard page for the account and check these two pages:

* **Activity Log**: the exact action and the game's reply.
* **Settings**: the **Pace, rest hours and limits** card and the **Expert mode** link for advanced values.

You can also run the account in **DRY-RUN** first. Dry-run shows every action Vanguard would take without sending it, so you can spot problems safely.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.