Troubleshooting

The machine never appears in the connected list.

Likely cause

The agent is not running, or it was signed in with a different Discord account.

Check

Open the agent on that computer and read which account it is signed in as.

Resolution

Sign in with the Discord account that owns your Kovex data, then wait for the machine to appear.

The machine was online this morning and is offline now.

Likely cause

The computer slept, lost network, or the agent was closed.

Check

Compare the last seen time with when you last used the computer.

Resolution

Wake the machine, start the agent, and disable sleep on computers that run unattended work.

A second computer will not stay connected while another one is online.

Likely cause

Your plan allows a set number of connected agents, and your other computers are using them.

Check

Open Downloads and look at the connected agents.

Resolution

Close the agent on a computer you are not using, or Revoke it on Downloads. The waiting agent connects once a slot is free.

Start is unavailable and mentions that no agent is connected.

Likely cause

There is no online machine to run the client.

Check

Look at the connected machines list.

Resolution

Bring a machine online, then start the account again.

The status becomes Error immediately.

Likely cause

The client could not start on that machine.

Check

Read the message on the account row, then confirm the client is installed where the agent expects it.

Resolution

Correct the client path in the agent, then start again.

A Jagex account is rejected at login.

Likely cause

The Jagex check failed. That can mean the stored session expired, or the account's proxy could not reach Jagex.

Check

Open the profile and look at the session state.

Resolution

Test the account's proxy, then re-authenticate the account and start it again.

The row says the launch failed, timed out, or the client exited before it was ready.

Likely cause

The client stopped while it was starting. On a current agent, the row shows the client's own reason.

Check

Read the full message on the account row, and check the agent is on its latest version.

Resolution

Update the agent, check the client's location in the agent's Paths tab (OnlyBot and TitanClient need none), and make sure the client opens by hand on that computer. If the message names nothing you can change, contact support with it.

The client opens, but the account sits at the login screen or Play Now.

Likely cause

The client or script in use may not log in automatically with the account's current settings.

Check

Note which client and script the account runs, then start that client by hand with the same script and see whether it logs in.

Resolution

Check that client's auto-login settings using the fixes below, or log in manually. If the client logs in by itself when started by hand but not from Kovex, contact support.

A TwiLite account waits at the login screen.

Likely cause

TwiLite's Login plugin waits for a primary script by default.

Check

Check whether the account has a primary script set.

Resolution

Set a primary script, or turn off the Login plugin's only alongside primary option.

An OnlyBot account never logs in, and the launch ends after a few minutes.

Likely cause

OnlyBot logs in through its script, so a script name that matches no installed script never starts.

Check

Compare the script name on the account with the installed script's name.

Resolution

Use the installed script's exact name, then start the account again.

A Ghost account sits at the Ghost login screen, or shows logged out while it is in game.

Likely cause

Ghost logs in by itself from version 0.0.359, and reports account details only while a script runs.

Check

Check the Ghost version on that computer and whether the account has a script.

Resolution

Update Ghost to 0.0.359 or later, and set a script on the account.

Start says the agent is at max capacity.

Likely cause

That agent is already running as many clients as its capacity allows.

Check

Look at how many clients that agent is running.

Resolution

Stop a client on that agent, or start the account on another agent.

Start says the account is already running or is currently being launched.

Likely cause

A launch for that account is still in progress, or its client is still open.

Check

Look at the account's status on the Accounts page.

Resolution

Wait for the current launch to finish, or Stop the account before starting it again.

Start says the account is banned.

Likely cause

The account is marked as banned, so it is not launched.

Check

Confirm the account's real state in the game.

Resolution

Only if you are sure it is not banned, unban it on the account, then start it again.

Start says instance launching is restricted.

Likely cause

A restriction is set on your Kovex account, and only staff can review it.

Check

Note when the message first appeared.

Resolution

Open a support request from the Support page so staff can review it.

A TwiLite launch ends with exit code 4 or 7, or the client closes about two minutes after logging in.

Likely cause

The agent cannot find the TwiLite runtime, usually because its path points at a folder that only holds the launcher.

Check

Open TwiLite once by hand and note the folder it runs from.

Resolution

Keep twilite-launcher.exe in the folder TwiLite installed to, then leave the TwiLite path in the agent blank or point it at that folder.

OnlyBot reports [-3] Database not available.

Likely cause

The OnlyBot launcher was not ready when the account started.

Check

Look for the OnlyBot tray icon, and check your accounts are listed in OnlyBot.

Resolution

Fully close OnlyBot including its tray icon, reopen it, sign in, confirm your accounts are listed, then Start again.

OnlyBot says the Jagex session has expired and could not be refreshed.

Likely cause

OnlyBot shows this whenever a Jagex check through the account's proxy fails, so the session is not always expired.

Check

Look at OnlyBot's own announcements for an outage, then test the account's proxy.

Resolution

Re-authenticate the account only when OnlyBot is up and the proxy test passes.

World, GP, membership days or account type stay blank for OnlyBot accounts.

Likely cause

OnlyBot does not provide those details.

Check

Confirm the account runs on OnlyBot.

Resolution

No action is needed. Those fields stay blank on OnlyBot.

A TitanClient account will not start, or new accounts from the account creator fail on their first Start.

Likely cause

TitanClient needs an activated Titan license on that computer, and accounts made by the account creator start on TitanClient.

Check

Confirm the Titan license is activated on the computer that runs the agent.

Resolution

Activate the license, or change those accounts, or their category, to a client you use.

TitanClient shows no game window on a server or remote desktop.

Likely cause

TitanClient runs the official game client, which needs a graphics card.

Check

Open the official game client by hand on that computer.

Resolution

If it does not open there either, run these accounts on a computer with a graphics card.

A BotClient account shows a black or magenta view on Live.

Likely cause

The BotClient window is not drawing the game.

Check

Look at the BotClient window itself on that computer.

Resolution

If it is black there too, Stop the account and Start it again. If the window shows the game but Live stays black, contact support.

An account is set to DreamBot.

Likely cause

DreamBot is no longer supported.

Check

Find the accounts or categories that use DreamBot.

Resolution

Move those accounts to a supported client with Edit Settings, or change the category's client.

An account shows Running but no card appears.

Likely cause

A machine filter is applied, or the client has not reported yet.

Check

Clear the machine filter and wait for the first report.

Resolution

If nothing arrives, stop the account and start it again.

A card is frozen on an old image.

Likely cause

The client closed, or the machine dropped offline.

Check

Refresh the preview and check whether the machine is still connected.

Resolution

Restart the agent if needed, then start the account again.

Live freezes while a client is minimized, or shows a script window instead of the game.

Likely cause

Minimized windows cannot be captured.

Check

Look at the client window on that computer, and check streaming is on in the agent's Settings.

Resolution

Keep client windows restored rather than minimized. Covered or background windows are fine.

An account still shows Running after its client closed.

Likely cause

The client closed without reporting that it stopped.

Check

Confirm the client is no longer open on that computer.

Resolution

Use Stop on the account rather than restarting the agent. If Stop does not clear it, contact support.

A proxy test fails on the website path but passes on the game path.

Likely cause

The route is refused by site protection, which creation and appeals depend on.

Check

Re-test and read both lines of the result.

Resolution

Use a higher quality route for creation and appeals. Launching can continue on the existing proxy.

Every proxy suddenly shows as blocked.

Likely cause

The machine that tests them lost its network, so every attempt failed.

Check

Confirm the machine has internet access, then test one proxy again.

Resolution

Fix the local network, then unblock the proxies you still want to use.

Start says the assigned proxy could not be found.

Likely cause

The proxy on that account was deleted.

Check

Open the account and look at its proxy.

Resolution

Assign another proxy to the account, then start it again.

Creation fails while waiting for verification mail.

Likely cause

The email source is misconfigured, or delivery is delayed.

Check

Open Email Setup and test the provider you selected.

Resolution

Fix or replace the provider, then queue a small run to confirm.

Webmail shows an empty inbox for a new account.

Likely cause

You signed in with the wrong address, or the mail has not arrived yet.

Check

Copy the address from the account profile and sign in with that exact value.

Resolution

Refresh after a short wait. If it stays empty, re-test the email provider.

Creation says the daily account creation limit was reached.

Likely cause

Your plan allows a set number of new accounts per day.

Check

Look at how many accounts you created today.

Resolution

The count resets at midnight UTC. Premium has no daily limit.

Creation says a paid plan is required, or that creating several at once is not available on your plan.

Likely cause

Creating accounts needs a paid plan, and creating several at once needs Premium.

Check

Look at your plan on the Subscription page.

Resolution

Create one account at a time, or change your plan.

Several creations at once keep failing.

Likely cause

Running creations in parallel lowers the success rate of each one.

Check

Compare your parallel runs with a run of one at a time.

Resolution

Create one account at a time with the default wait.

Creation cannot start on any agent.

Likely cause

Account creation needs browser automation and account creation switched on in the agent.

Check

Open the agent's Settings on the computer you want to use.

Resolution

Switch on browser automation and account creation, then queue the run again.

The checker panel says checking is off everywhere.

Likely cause

No connected machine has login checking enabled.

Check

Open the agent settings on the machine you intend to use.

Resolution

Switch account checking on, then queue the run again.

Results come back as proxy errors or timeouts.

Likely cause

The routes used by those accounts are failing, not the credentials.

Check

Test the proxies assigned to the affected accounts.

Resolution

Replace the failing routes, then re-check only those accounts.

Appeals cannot start and mention browser automation.

Likely cause

No connected machine has browser automation enabled.

Check

Read the enabled machine count in the appeals panel.

Resolution

Switch browser automation on in the agent, then run the appeal again.

A run stops at a human verification challenge.

Likely cause

The site asked for interactive verification on that machine.

Check

Look at the browser window the agent opened.

Resolution

Complete the challenge there, or retry later from a better route.

A job says another browser automation job is already active on this agent.

Likely cause

Each agent runs one browser job at a time, such as a creation, a sign-in or an appeal.

Check

Open the Queues tab and look for a running job.

Resolution

Let the running job finish, then try again. If nothing is running and the message stays, contact support.

A rule never starts any accounts.

Likely cause

The rule is off, its max concurrent is zero, or no agent is free to launch on.

Check

Open the rule and read its status and max concurrent, then check the agent is online and not at its client limit.

Resolution

Enable the rule, set max concurrent above zero, and bring an agent online with free capacity. If all of that checks out and the rule's history shows nothing, contact support.

Fewer accounts start than the rule allows.

Likely cause

Accounts started by hand in the source category count toward the rule's max concurrent.

Check

Count the running accounts in the source category.

Resolution

Stop manual launches you no longer need, or raise max concurrent.

The import says it has too many accounts, or that the file is too large.

Likely cause

Each import has a size limit.

Check

Count the lines in your file.

Resolution

Split the list into smaller imports.

Lines are skipped as duplicates, as already existing, or as missing an email or password.

Likely cause

Each line needs one complete account, and accounts you already have are skipped.

Check

Read the skipped lines in the import result.

Resolution

Use one account per line as email:password or email:password:totp. The other lines still import.