Sign-in problems

Asterobot deals with two sign-ins that have nothing to do with each other. It signs itself in to your asterobot.net account, with a code you confirm on the website, and it signs in the Ankama accounts your Full socket bots play with. A bot in MITM mode needs no Ankama sign-in in Asterobot: you sign in yourself, in Dofus.

asterobot.net

Sign in with asterobot.net explains how the code works when everything goes right.

Clicking Sign in does nothing

The account button stays on Sign in, and no link comes. Either Asterobot asked asterobot.net for a code and didn't get one, or your click never reached Asterobot. Asteroboard shows no message in both cases.

1. Check that Asteroboard is connected: no red dot on Preferences in the sidebar. If there is one, see Asteroboard can't connect.
2. Look in Asterobot's terminal, or on Server > Console, for the warning Failed to request a sign-in code, followed by the reason.
3. Check that the computer where Asterobot runs can reach asterobot.net, and look at https://status.asterobot.net.
4. Click Sign in again.

Sign-in pending, but no tab opened

Asterobot opens a browser tab by itself only for the first code after it lost its sign-in, and only on the computer where it runs. On a machine without a desktop, the terminal shows Failed to open the web browser instead. The code is waiting all the same.

• Click the account button, which reads Sign-in pending: it opens the sign-in link in a new tab, on the device you're using.
• Or copy the link from the terminal, on the line after Website sign-in required. Please visit this link to authorize access to your account; the app will continue automatically once authorized.
• Or turn on website.showQRCode on Server > Config, and scan the QR code the terminal shows with the next code.

Sign-in was not completed in time; it will be offered again

Asterobot stopped waiting for the code. Either nobody confirmed it within 15 minutes, or someone refused it on asterobot.net: both end with this same line. The account button goes back to Sign in, and Asterobot asks for a new code by itself within a few minutes.

1. For a new code right away, reload Asteroboard. If the account button reads Sign in, click it.
2. Open the new link and confirm the code within 15 minutes.

This code is invalid or has expired. Check the code displayed on your device and try again.

asterobot.net shows this when the code doesn't match a sign-in that's waiting: it was mistyped, it was already used, or it's more than 15 minutes old.

1. Compare it with the code at the end of the link, after code=. A code has eight characters, digits and letters from A to F. Spaces, hyphens and small letters don't matter.
2. If it's older than 15 minutes, get a new one as described in the previous section.

Too many incorrect codes have been entered. Wait a few minutes and try again.

20 codes that didn't match any waiting sign-in were typed from your internet connection within 15 minutes, and asterobot.net stopped checking codes from that connection for a while. A code that doesn't have the right format doesn't count.

1. Stop typing codes.
2. Wait. You can type codes again at most 15 minutes after the last wrong one.
3. Open the link from the account button instead of typing the code: it carries the code for you.

The authorization was denied. You can close this page; your device will stop waiting shortly.

Someone refused access to Asterobot on asterobot.net's authorization page. Asterobot stops waiting and prints Sign-in was not completed in time; it will be offered again. If that was a mistake, get a new code and allow access this time.

Start again from your device.

Three messages on asterobot.net end this way:

• This authorization link is invalid or has expired. Start again from your device.
• This authorization session has expired. Start again from your device.
• The authorization could not be completed. Start again from your device.

The page was opened from an outdated or damaged link, the code expired while you were signing in, or asterobot.net couldn't finish. Open the newest link from the account button. If the button reads Sign in, click it for a new code.

Website rejected the token

asterobot.net stopped accepting Asterobot's sign-in, for example because it expired or was revoked. Asterobot forgets it and starts a new sign-in at once: after this warning, the terminal shows a new link, and the account button switches to Sign-in pending. Confirm the new code.

Asterobot stays signed out after a restart

After Log out on the account button, or Disconnect on the Account page, Asterobot doesn't sign back in by itself, not even when it restarts. Click Sign in on the account button. See Your account.

Asterobot is signed in with the wrong account

The code is confirmed for whichever account your browser is signed in with on asterobot.net at that moment. Log Asterobot out, sign in to the right account on the website, then click Sign in again. Your account goes through it.

Signed in, but bots are refused

When Asterobot is signed in and still refuses to add or connect bots with this installation is not entitled to start bots, see Bot doesn't connect.

Ankama accounts

Automatic sign-in and Manual sign-in explain both ways of signing an account in.

Sign in automatically isn't in the menu

Sign in automatically only appears for an account with a stored password. Open the account's menu, click Connect, then store the password with Store an Ankama password for automatic sign-in at the bottom of the dialog. See Manual sign-in.

Automatic sign-in failed: ankama account authorization required

After Automatic sign-in failed, the message starts with ankama account authorization required, followed by the address of Ankama's sign-in page, and ends by asking you to save a code to the configuration. Ignore that end: signing in happens in Asteroboard's dialog. The message is the same whatever went wrong, so find the real reason first.

1. Open Asterobot's terminal, or Server > Console.
2. Look for the warning Automatic Ankama sign-in failed, a person has to sign in. Its error starts with browser sign-in failed:, then says what happened.
3. Find that text in the table below.

When you started the attempt with the dialog's own Sign in automatically button, the dialog also shows a picture of the page the browser was on when it gave up. It's often the fastest way to tell a captcha from a wrong password.

Ankama asks for a person

Ankama sometimes puts a challenge or a captcha in front of its form, and automatic sign-in doesn't try to get past it. You have two ways out:

• Sign in manually, in your own browser, from the account's sign-in dialog, below "or sign in yourself". This works wherever Asterobot runs. See Manual sign-in.
• Answer it in the sign-in browser's window, when Asterobot runs on a computer you're sitting at: turn off zaapmanager.browserHeadless on Server > Config, start the automatic sign-in again, answer quickly in the window that opens, then turn the setting back on. See Automatic sign-in.

Sign in automatically seems stuck

A sign-in through the browser can take up to two minutes. Ankama sign-ins also happen one at a time across all your accounts, so an account waits while another one signs in. Wait for the result before you click again.

Couldn't start the sign-in

Open Ankama sign-in failed. The first time Asterobot prepares an Ankama sign-in after starting, it fetches the current Ankama Launcher version from Ankama, and that step didn't work. Check the internet connection of the computer where Asterobot runs, then click Open Ankama sign-in again.

Couldn't complete the sign-in - the code may have expired, try again

Asterobot couldn't trade what you pasted for the account's sign-in. A code works once, and only for the sign-in it was created for. The common causes:

• The link was copied incompletely, or it's the address of Ankama's Congratulations page rather than the link behind its Continue button.
• The code was already used, or comes from an older tab: each click on Open Ankama sign-in starts a new sign-in, and only its own code matches.
• Asterobot restarted after you clicked Open Ankama sign-in.

1. Close the dialog.
2. Open it again from the account's menu and click Open Ankama sign-in.
3. Sign in, right-click Continue, copy the link address, which starts with zaap://login?code=, and paste it in Authorization code.
4. Click Submit.

The same message appears when Asterobot refuses tokens typed in Enter tokens manually instead (debug), for example an expiry date it can't read.

Verification failed - try reconnecting

Verify asked Ankama, the account's sign-in didn't work, and Asterobot couldn't repair it: the quiet renewal was refused, and a browser sign-in wasn't possible or failed too. Click Reconnect in the account's menu and sign in again.

Couldn't refresh the token - try reconnecting

Ankama refused Force refresh token, or the account has no refresh token. This action never falls back to the browser. Click Reconnect and sign in again.

The account shows Signed in, and bots fail with ankama account authorization required

Signed in only means Asterobot holds the account's tokens, not that Ankama still accepts them. When a bot connects, Asterobot uses the sign-in for real: it renews it quietly when Ankama allows, signs in again through the browser for an account with a stored password, and otherwise the connection fails with this message.

1. In Account Manager, click Verify in the account's menu.
2. If it fails, click Reconnect and sign in.
3. Connect the bot again.

When the account has a stored password and still fails, Asterobot's log gives the reason, as described in Automatic sign-in failed.

Accounts with Ankama Shield or two-factor authentication

These accounts can't be used in Full socket mode: automatic sign-in can't answer the extra step, and Full socket mode doesn't support them even when they show Signed in. Use MITM mode, where you sign in yourself in Dofus. See Shield and two-factor authentication.

Where to go next

• Bot doesn't connect
• Account status and actions
• Getting help