The bot stopped and shows an error
The bot stops on its own when retrying can't help:
- banned: the server banned the account. Contact the server's staff.
- not_whitelisted: the server only allows approved players.
- auth: Microsoft sign-in failed or expired, or the account doesn't own Minecraft Java. Start the bot again and complete the new code.
- ssid_expired / ssid_rejected: the bot signs in with an SSID token and it ran out (they last about 24 hours) or Mojang rejected it. Open the bot, go to Settings, and paste a fresh token, or switch the bot to Microsoft sign-in.
- max_retries: the bot couldn't reconnect after many attempts. The server may be down. Start it again later.
Using an SSID token
An SSID is the access token your launcher holds for a logged-in session. Paste it in the bot's Settings under Sign-in method. We check it with Mojang, then store it encrypted and never show it again. Tokens last about 24 hours, so IdleForge sends a Discord alert an hour before it runs out. For a bot that should stay online for weeks, use Microsoft sign-in instead.
It keeps reconnecting
Open the console and read the line before each reconnect. Common causes are a server restart, a kick for being idle (try a stronger anti-AFK preset), or a version mismatch (set the version in the bot's settings).
It won't connect at all
- Check the address. Use the same one you use in the game, without
http://. - If you set a proxy, test without it. A dead proxy blocks the connection.
- Check the status page.
Still stuck? Contact us with the bot name and the last few console lines.