Troubleshoot a connection or feature
Find the useful error first, then check authentication, proxies, server settings, or automation.
Start with one account and its error
Check the account’s status and error details in Overview, then open Chat → Console. Keep the exact error text. Test one account while changing one setting at a time so you can tell which change helped.
Account will not connect
| Symptom | Next check |
|---|---|
| Authentication failed or code expired | Finish the current Microsoft prompt with the right account. Imported tokens may need a fresh authorized export. |
| Waiting for a proxy or proxy connection error | Check proxy assignment, credentials, availability, expiry, and bandwidth allowance. Bedrock also needs UDP support. |
| Cannot reach the Minecraft server | Confirm the edition-specific host and port under Settings → Connection. Check any account-specific override too. |
| Version or protocol error | Select a version supported by both the dashboard and your Minecraft server. |
| Session conflict or logged in elsewhere | Disconnect that Minecraft account from another client or connection before retrying. |
| Repeated server kicks | Read the kick reason before retrying. Review enabled behavior and server requirements; repeated reconnects do not fix the underlying rejection. |
Connected, but the feature does nothing
Check the feature’s master toggle, selected accounts, edition support, and plan requirement. Wait for the save confirmation. Look for another macro, open inventory window, or movement action that conflicts with the setup.
| Feature | Specific checks |
|---|---|
| Sell Axe | Correct sell axe held, chest in view and reach, Sell Axe assigned, right-click and sneak settings. |
| Spawner Sentry | Connected account, reachable spawners, supported standing block, pickaxe, inventory space, activation count, block whitelist, ignore radius and max distance. With Player Detection on, also the Friends list and its own max distance. The alert title and the console show which detection started a run, see Which detection started the run? |
| Join command | Global or account-specific command, enabled toggle, correct home name, sufficient join delay. |
| Discord alerts | Correct destination, event enabled, account selected, and successful Send test. For Discord Bot: Tier 3, bot online, selected server, channel send/embed permissions, and Attach Files for screenshots or logs. See Discord alert troubleshooting. |
| Macros | The account is connected, the run is listed under Active Macros, the step order and delays are right, and Stop on error is not ending it early. The [macro] lines in Chat → Console say which step failed and why. See the macro guides. |
| Macro Recording | Tier 2, a saved recording, an account of the same edition, and a start the account can reach. The playback’s message in Chat → Console says what stopped it and when; see when a playback stops. |
Share useful details with support
If the problem persists, note the affected feature, Minecraft edition and server, account status, exact error, and the steps that reproduce it. A cropped screenshot of the relevant settings can help. Keep passwords, cookies, tokens, and webhook URLs out of screenshots and messages.
Check service status and use the support link on the Console Client website.
Check the service status or return to all guides.