MITM problems

In MITM mode, short for man-in-the-middle, a bot relays the Dofus client you play: Asterobot points your game at itself by changing one line in your Dofus folder, then passes everything on to Ankama. Most things that go wrong here show no reason in Asteroboard, so this page lists the causes to check, in the order they usually happen. MITM mode explains how the mode works.

Couldn't put the bot into waiting

Asteroboard shows Couldn't put the bot into waiting when you click Start waiting, or Bot added, but it couldn't be connected when you add a bot with Wait for my game client. The bot stays Disconnected. Asterobot refused, but the reason isn't shown in Asteroboard or written in the log, so go through the causes:

Then click Start waiting again.

After an Ankama patch, the version is the usual culprit: the Ankama Launcher updated your Dofus, and Asterobot still has the previous version. Download the new one and move the bot to it, as When Dofus updates explains.

The bot waits, but your game never reaches it

The bot shows Waiting for your game client while you play, and nothing arrives. Check these in order.

Asterobot didn't change the line

When the first bot starts waiting, Asterobot's log, in the terminal and on Server > Console, shows Pointed the played game at Asterobot. A second waiting bot doesn't print it again, so look further up if another bot was already waiting.

When the line never appears, botmanager.mitmGamePath is empty. On macOS it always is at first, since there's no default, and elsewhere it's empty when Dofus wasn't in the Ankama Launcher's usual folder as Asterobot started. The bot waits anyway, but nothing is edited and your game never comes.

1. On Server > Config, set botmanager.mitmGamePath to your Dofus folder, the one that contains Dofus_Data.
2. Click Disconnect on every waiting bot, then Start waiting again.
3. Check that the log now shows Pointed the played game at Asterobot.

See Where Asterobot looks for your Dofus folder.

Dofus was already open

A Dofus started before the bot was waiting doesn't go through Asterobot. Close it, and start it again from the Ankama Launcher.

A game client signed in that no bot is waiting for

Your game went through Asterobot, but no waiting bot took it, and it went straight to Ankama. Each bot takes sessions by Ankama account: a bot that relayed an account once only takes that account's sessions from then on. A bot without an Ankama account stays attached to its first account for good, even after a restart, and Asteroboard has no way to detach it.

• Play with the account the bot is attached to. Its Information tab shows the account once a session has arrived.
• To relay another account, add another bot without an account and click Start waiting on it.

See Which bot gets which game session.

Dofus runs on another computer

Asterobot can only edit a Dofus folder on its own computer. For a game on another computer, you change the line there yourself and open Asterobot's ports: see MITM across machines.

Dofus can't sign in

Asterobot isn't running

While a bot waits, the ConfigUrl line of your Dofus folder points at Asterobot. If Asterobot then stops without closing properly, for example because its terminal window was closed, the line stays that way and Dofus can't sign in at all.

1. Start Asterobot again. As it starts, it puts the line back and prints Restored a game install left pointing at Asterobot by a previous run.
2. Start Dofus.

Asterobot reads the original line from its own copy of the game, which it finds through your bots. If it doesn't print that line, for example because every bot was skipped as it started, or because botmanager.mitmGamePath is empty, put the line back by hand as described below. A bot that starts waiting also repairs the line first, and prints Recovering a ConfigUrl left pointing at Asterobot by a previous run.

Stopping Asterobot with Ctrl+C or Shutdown server puts the line back at once, and so does disconnecting the last waiting bot.

HTTPS or a password is set

MITM mode doesn't work while server.tls is on or server.basicAuth holds anything, even with Dofus and Asterobot on the same computer. The line Asterobot writes always tells Dofus to fetch its connection settings over plain http://, without a password. With HTTPS, Asterobot's port only answers HTTPS requests, and with basic auth it asks for a password Dofus can't give. Either way, Dofus doesn't get its connection settings and can't sign in through Asterobot.

1. On Server > Config, turn off server.tls and click Reset to default on server.basicAuth.
2. Restart Asterobot.
3. On the computer where Asterobot runs, open http://127.0.0.1:8080, so Asteroboard uses the plain address again.
4. Click Start waiting, then start Dofus.

To use Asteroboard from another device and keep MITM mode, use an SSH tunnel instead of HTTPS: see Asterobot on a remote machine.

Failed to fetch the real game configuration

When Dofus asks Asterobot for its connection settings, Asterobot fetches Ankama's real ones and changes the sign-in address in them. This error in the log means it couldn't reach Ankama for that. Failed to reach the Ankama login server means the same for the sign-in itself. Check the internet connection of the computer where Asterobot runs, then start Dofus again.

Put the line back by hand

When Asterobot can't restore your Dofus folder, you can do it yourself:

1. Close Dofus.
2. Find Asterobot's own copy of the same game version, in Asterobot's cache folder, under game/dofus/dofus3/windows/ followed by the version number. Files and folders shows where the cache folder is. Asterobot never edits that copy. If the version isn't there any more, download it again in Game Manager first.
3. Open that copy's Dofus_Data/StreamingAssets/version file and copy its ConfigUrl= line.
4. In your own Dofus folder, open Dofus_Data/StreamingAssets/version with a text editor, and replace its ConfigUrl= line with the one you copied. Leave the other lines as they are.
5. Save the file and start Dofus.

A ConfigUrl line that ends with /botmanager/mitm/dofus3.json is one Asterobot wrote. The line Asterobot changes explains it.

Your game is disconnected as it reaches the bot

You sign in, and the game disconnects as it enters. Asterobot's log shows Failed to relay a game session, followed by the reason.

• The reason mentions dial the real game server: Asterobot couldn't reach the game server. Check the internet connection and the firewall of the computer where Asterobot runs.
• Right after an Ankama patch, your release of Asterobot may not support the new version yet. See When Dofus updates.

Your game is disconnected while you play

The bot carries your session, so whatever ends the bot's session ends your game:

• Disconnect on the bot, Delete bot, or stopping Asterobot.
• A package that closes the game connection. Click Stop and play without it to find out.
• Another Dofus signing in with the same Ankama account: the new session replaces the one the bot was carrying.

When you quit Dofus, the bot goes back to Waiting for your game client, and a running script stops with The behavior stopped with an error. That's expected: press Play again once your game is back.

Scripts on a relayed session

Refused to forward a message that would re-authenticate a relayed session

This warning appears in the bot's Console tab. The script sent IdentificationRequest, the message a Full socket connection script sends to enter the game. Your Dofus already did that, and sending it again would end your session, so Asterobot didn't forward it. The script keeps running.

When the script waits for an answer to that message instead, it gets mitm relay refuses to identify: this Game session was already authenticated by the real DOFUS client, and stops with The behavior stopped with an error unless it handles the error.

A connection script should only identify on its first launch, when launch.reason is "initial", which never happens on a relayed session. If you wrote it, see Identify and run. If you didn't, tell its author.

interceptor failed:

A package can change or block the messages between your game and the server. This error line in the bot's console means one of the functions doing that threw an error or ran for more than 250 ms: the message went through unchanged, and the script keeps running. A function written as async behaves differently: it always lets the message through, and when it fails, the whole script stops with unhandled Promise rejection: in The behavior stopped with an error.

Either way, the package has a bug. Tell its author, or see Intercepting if it's yours.

What the bot shows makes no sense

When your Dofus and the bot's game version differ, Asterobot reads your game's messages with the definitions of another version: names, fields and items can look plausible and still be wrong. On a single computer, Asterobot refuses to wait in that case. Across machines, nothing checks it: compare the Version= line on the Dofus computer with Game Manager after every Dofus update.

Where to go next

• MITM mode
• MITM across machines
• Package errors