Frequently Asked Questions

Find answers to common questions about MinecraftAfkBots

HomeFAQConnection troubleshooting

Connection troubleshooting

If your bot is having trouble connecting to a server, this guide covers the most common causes and how to fix them.

Check the server address

The most common cause of connection failures is a typo in the server address. Double-check that the address and port are correct. If the server uses the default port (25565), you usually do not need to specify it.

play.example.com:25565

Check the Minecraft version

MinecraftAfkBots auto-detects the server version in most cases. However, some servers using protocol hacks or custom software may not respond correctly. Try manually setting the version to match the server in your account settings.

See supported versions for the full list of compatible versions.

Server is blocking connections

Some servers actively block bots, headless clients, or datacenter IPs. Signs of this include:

  • Immediate disconnection after joining
  • Kick message mentioning "VPN", "proxy", or "bot protection"
  • Being sent to a captcha or verification lobby

In these cases, try using a residential proxy or check if the server allows bot connections. See VPN blocks for more details.

Microsoft account issues

If the error mentions authentication or your Microsoft token, try re-authenticating your Minecraft account:

Warning:Microsoft tokens expire periodically. If your bot was working before but suddenly stopped, re-authentication is usually the fix.

Server is offline or restarting

If the server is down for maintenance or restarting, your bot cannot connect until it comes back. Enable auto reconnect so your bot automatically reconnects once the server is available again.

Still having issues?

If none of the above solutions work, check the common error messages page for specific error codes, or contact us at support@mcbotpanel.com with your account details and the error message you are seeing.

Tip:Include a screenshot of the error or the exact error text when contacting support. It helps us resolve your issue much faster.

Last updated: February 2026