Fix connection problems

Every account on a profile's Connect page shows a status, and sometimes a small button beside it. Between them they say what the account is doing and, when it isn't online, why. This page goes through each of them, then through the popups and the logs.

Statuses

The status badge is also a button. Hover it to see what a click does.

Three badges take the place of Offline when a plain connect wouldn't help:

• Re-authenticate (red): Microsoft has ended this account's login, so it can't connect. Click it: it tries to restore the login by itself first, and if that doesn't work, asks you to sign in again with the Microsoft account this Minecraft account belongs to.
• Stopped by macro (red, with a siren): a macro's panic logout took the account off the server. Hover it to see which macro stopped it and why. Clicking it reconnects the account and starts the macro again. See Starting again after a stop.
• Offline with a ban symbol in it: the account is already online from another of your profiles for the same server. See Already connected elsewhere.

Click the Status column's header to sort by it. Left alone, the table keeps the accounts in name order, pinned ones first, so a row never jumps when its status changes.

Logging in one at a time

Your accounts don't all log in at once. They take turns, across all of your server profiles, with at least 5 seconds between one login and the next. So when you connect a long list, most of it shows Connecting for a while, and Connect Selected's message says how many accounts were queued rather than connected. Twenty accounts take well over a minute.

If a server kicks accounts for joining too quickly, make the gap longer: switch on Join delay in the profile's Settings, under Extra settings. Each of that profile's accounts then waits that long after the previous login before it joins. The shortest it can be is the same 5 seconds. See Extra settings.

Warnings beside the status

The small buttons beside a status are shortcuts. Hover one to read it, click it to go where the fix is.

The yellow warning stays until the account reaches Online, or until you reload the page. Dismissing a popup, stopping the account or trying again doesn't clear it, so an account that keeps failing stays flagged. A macro's panic logout never raises one, since the Stopped by macro badge already says what happened.

Connection error popups

For six kinds of failure, a popup also opens, with the server's own message and what you can do about it. It only opens on the Connect tab of the profile it is about. Anywhere else, a red dot on that profile in the sidebar, and on its Connect tab, tells you one is waiting. Accounts that hit the same error share one popup.

Dismiss closes the popup, and so do Escape and clicking outside it. Stop connecting (or Stop all, when several accounts share the popup) stops those accounts trying again.

MinecraftAFK has a partnership with Minecadia. When Minecadia's anti-VPN catches your accounts, the popup says to contact their support in their Discord and tell them you're using MinecraftAFK, and they'll let the accounts through. Contact Minecadia opens their Discord. A held login there gets Open Minecadia Discord instead, for the confirm DM.

Once you dismiss a popup, the same failure doesn't open it again. A new failure on the same account can, but not within 15 minutes of the last one.

To stop the popups on one profile, switch on Mute error popups in its Settings, under Manage dangerous settings. That profile then gets no popups and no red dot in the sidebar, but the yellow warning beside the status stays, so a failing account is still flagged on the Connect tab.

When auto reconnect waits or stops

Auto reconnect brings an account back after a drop, waiting the delay you set. It doesn't chase a kick that no retry can fix, and a few kicks make it wait longer than your delay. The account's logs say which one happened.

• Stopped: the server says the account is permanently banned, or that you already have as many accounts online there as it allows. Reconnect it yourself once that is sorted out. A temporary ban is retried as usual.
• Waits at least 5 minutes: the server still shows the account online from its last session, which clears by itself.
• Backs off, up to an hour: the server is holding the login for you to confirm. Once you have, connect the account yourself and it tries straight away.
• Retries, then stops: the server rejects the account's version. A server that is restarting does this too, so it tries a few more times over about half an hour before it gives up.

Account logs

Every account keeps a log of its connection activity: each connect, kick, retry and reconnect, with the time and the server's own message. Open it from the yellow warning, or with View logs in the row's ⋮ menu or its right-click menu. It updates by itself while it's open.

Copy puts the whole log on your clipboard, and Download saves it as a text file. Send that along when you ask for help. If the account has lost its Microsoft login, the log says so at the top, with a Re-authenticate button.

Already connected elsewhere

Minecraft allows one session per account, so an account can only be online from one of your profiles for a given server at a time. A second login would kick the first bot, and with auto reconnect on the two would spend the day kicking each other.

So the dashboard refuses it. An account that is online or connecting from another profile for the same server shows a ban symbol in its Offline status, and hovering it names that profile. Clicking it opens a popup saying the account "is already connected elsewhere", with a button to open the profile that holds the session. Connect Selected leaves those accounts out and connects the rest. Disconnect the account on the other profile first, then connect it here.

Two profiles count as the same server when their addresses match, ignoring capital letters and a :25565 port. A different subdomain or a different port counts as a different server. Having one account on two profiles for the same server is fine; only having both online at once is not.

If both are online anyway, for example because they were connected from two tabs at the same moment, a warning above the table says so until one of them goes offline. Disconnect it on one of the two profiles.

The same rule covers you. Logging in to an account in your own game while its bot is online kicks one of the two, and with auto reconnect on, the bot logs back in after its delay. Disconnect the account first.

Locked server profiles

Your plan includes a set number of server profiles (see Limits by plan). If you have more than that, for example after a downgrade, the profiles past the number are locked. Which ones follows the order of your server list: the profiles at the top stay usable, and the ones further down are locked. See After a downgrade for what else changes.

A locked profile keeps its settings and macros, but it can't connect. When a plan change locks it, the accounts on it are disconnected and taken off it, so add them back once it unlocks. It shows a lock in the sidebar where its online count would be, and its Connect Selected is greyed out: "This server profile is above your plan's limit. Upgrade, or move it higher in your server list, to connect it." Disconnect Selected still works.

To unlock one, upgrade, or open Reorder servers from any profile's menu and drag it above one you can do without. It unlocks as soon as the order is saved. Pinning a profile on the Servers page doesn't change which ones are locked: only the order you save in Reorder servers does.

Macros lock the same way within a profile, when it has more than your plan allows: see How many macros you can have.

If it still won't connect

• No plan yet: connecting opens Subscribe to connect accounts. Your profiles and accounts stay as they are, ready to connect once a plan is active. See Client access.
• A server you can't get onto at all: check the address with the server checker, and that you can join it from your own game.
• Anything else: download the account's logs and ask us.