Aller au contenu
Afficher dans l'application

Une meilleure façon de naviguer. En savoir plus.

Asterobot

Une application plein écran sur votre écran d'accueil avec notifications push, badges et plus encore.

Pour installer cette application sur iOS et iPadOS
  1. Appuyez sur Icône de partage dans Safari
  2. Faites défiler le menu et appuyez sur Ajouter à l'écran d'accueil.
  3. Appuyez sur Ajouter dans le coin supérieur droit.
Pour installer cette application sur Android
  1. Appuyez sur le menu à trois points (⋮) dans le coin supérieur droit du navigateur.
  2. Appuyez sur Ajouter à l'écran d'accueil ou Installer l'application.
  3. Confirmez en appuyant sur Installer.

Asteroboard can't connect

Asteroboard has nothing to show on its own: every bot, setting and game version on its pages comes from your Asterobot. When the two can't talk, pages stay empty and nothing you click goes through. The causes below start with the most common.

How to tell

Where What you see
A notification Server disconnected, with "Asteroboard lost connection to the Asterobot server. Retrying automatically…"
The sidebar A pulsing red dot on Preferences
Server > Status A red dot and Disconnected, or an amber dot and Connecting… while Asteroboard tries
Preferences, in the Server section The Disconnected badge next to Test connection
A bot's page "This bot isn't registered (or was removed)." with "It may have been removed, or the server it lives on isn't reachable."

Asteroboard tries to reconnect by itself, once a second, for as long as the page is open. It shows Server disconnected once when it loses Asterobot, not at every attempt, and Server connected once it's back. You don't need to reload the page.

To check right now, open Preferences, go to the Server section and click Test connection. It sends one request to the address in Server URL:

  • Server reachable, with a line such as "Round-trip latency: 12ms": Asterobot answered. If the badge didn't say Connected yet, Asteroboard reconnects at once.
  • Server unreachable: nothing answered at that address. Read on.

Asterobot isn't running

This is the most common cause. Asterobot stops when its terminal window is closed, when someone clicks Shutdown server, when Ctrl+C is pressed in its terminal, or when the computer restarts. Asteroboard can't start it again.

  1. Go to the computer where Asterobot runs and look for its terminal window.
  2. If there's none, start Asterobot again as First launch shows.
  3. Wait for Server listening in the terminal. Asteroboard connects by itself and shows Server connected.

Your bots come back disconnected, and nothing reconnects or plays on its own. See Disconnect, delete and restart.

An error occurred during the server's initialization process

Asterobot prints this and stops a moment after starting: it couldn't listen on its address. The rest of the line starts with failed to make server listen:, followed by the reason your system gave.

Two things can mislead you. The terminal shows Server listening right before the error, because Asterobot prints that line before it tries. And your browser may still open http://127.0.0.1:8080, which then shows whatever already uses that port: if it's another copy of Asterobot, you land on an Asteroboard connected to that other copy.

The usual causes:

  • Another copy of Asterobot is already running, in another terminal window, in a terminal multiplexer such as tmux, or as a service. Use that one, or stop it before starting a new one.
  • Another program uses port 8080. Give Asterobot another port, as below.
  • server.listenAddress names an address this computer doesn't have, for example a network address that changed since you set it. Set it back to 127.0.0.1:8080, or to the current address.

Since Asterobot isn't running, change the setting in config.toml with a text editor. Files and folders shows where the file is.

  1. Open config.toml.

  2. Add these lines, or change the value if a [server] section is already there:

    [server]
    listenAddress = "127.0.0.1:8081"
  3. Save the file and start Asterobot again.

  4. Open http://127.0.0.1:8081 in your browser, so Asteroboard picks up the new address.

In MITM mode, the line Asterobot writes in your Dofus folder follows the new port by itself. How the parts connect also covers the two MITM ports.

The Server URL points somewhere else

Asterobot runs, its terminal shows Server listening, and Asteroboard still stays disconnected. Asteroboard connects to the address saved as its Server URL in the browser you use, and that address doesn't lead to your Asterobot. It happens after you change server.listenAddress, when the browser still holds the address of another Asterobot, such as a remote one or an SSH tunnel on another port, or after a typo.

  1. On the computer where Asterobot runs, open http://127.0.0.1:8080 in the browser, with the port of server.listenAddress if you changed it. Asterobot sends you on to Asteroboard, which replaces its Server URL with that address.
  2. From another device, or to type the address yourself, open Preferences, type it in Server URL with the scheme, the address and the port, such as http://127.0.0.1:8080, and press Enter.
  3. Click Test connection.

Each browser keeps its own Server URL, one at a time. Preferences explains the field.

The address opens, but Asteroboard stays disconnected

This is almost always HTTPS or a password, set with server.tls and server.basicAuth. Asteroboard's own requests can't show a certificate warning or a password prompt, so they fail without a word until the browser has accepted both on a page you opened yourself.

What you see What to do
Client sent an HTTP request to an HTTPS server. server.tls is on, and the address starts with http://. Use https://.
Server disconnected right after a restart that turned server.tls on Asteroboard's Server URL still starts with http://. Open https://127.0.0.1:8080, accept the warning, and Asteroboard takes the new address.
Server unreachable, although the https:// address is right Open that address in a tab of the same browser, accept the certificate warning and enter a login and password from server.basicAuth. Then go back to Asteroboard.
It worked yesterday and stopped today Browsers forget the password when they close, and some forget the certificate choice after a while. Open the address again.
The browser keeps asking for the password The login and password must match a pair in server.basicAuth exactly.

Important

With server.tls on, or anything in server.basicAuth, MITM mode stops working. See MITM problems.

From a phone or another computer

By default, Asterobot only accepts connections from the computer it runs on, so another device can't reach it at all. Opening it to your network takes a few settings and a restart: Asteroboard on another device walks through them, and Asterobot on a remote machine covers a server.

When you've done that and it still doesn't connect, check these:

  • The address starts with https://. Browsers don't let the Asteroboard page, which is HTTPS, send plain http:// requests to another device. Only the device the browser runs on is allowed, which is why http://127.0.0.1:8080 works there and nowhere else. The other way around it is an SSH tunnel.
  • Asterobot was restarted after you changed server.listenAddress, server.tls or server.basicAuth. None of them applies before.
  • server.listenAddress no longer starts with 127.0.0.1, an address no other device can reach.
  • The firewall of the computer running Asterobot accepts incoming TCP connections on the port.
  • Your browser's permission. Some browsers ask whether asteroboard.asterobot.net can access devices on your local network. Allow it.
  • The SSH tunnel is still open, if you use one. When it closes, Asteroboard shows Server disconnected, and connects again by itself once the tunnel is back.

Asteroboard itself doesn't load

Asteroboard's page comes from https://asteroboard.asterobot.net. The first time you open it in a browser, that browser needs an internet connection. After that, Asteroboard opens without one, as long as it can reach Asterobot.

What you see What it means What to do
The page doesn't open at all The browser can't reach asteroboard.asterobot.net and has no copy of it yet. Check your internet connection, and https://status.asterobot.net.
Offline mode unavailable "This device couldn't get everything ready for offline use." Asteroboard works, but some features may need an internet connection. Nothing, unless you need it offline.
Update available, with Refresh now A new version of Asteroboard is ready. Click Refresh now, or reload the page.
An old version, or odd behavior after an update The browser's copy of Asteroboard is out of step. Use Reset offline data. See Reset and start over.
Page not found The address doesn't match any page of Asteroboard. Click Go to dashboard.
Something went wrong "Asteroboard couldn't display this page." Click Go back, or reload. If it keeps happening, open Technical details and note the Status and the Requested address for your help request.

Still stuck

  • Read Asterobot's terminal. Server > Console only receives lines while Asteroboard is connected, so the terminal is the only place that shows what happened before.
  • Ask on the forum or on Discord, with your Asterobot version, the address you use and the last lines of the terminal. Getting help lists what to include and what never to share.

Where to go next

Compte

Navigation

Recherche

Recherche

Configurer les notifications push du navigateur

Chrome (Android)
  1. Appuyez sur l'icône de cadenas à côté de la barre d'adresse.
  2. Tap Autorisations → Notifications.
  3. Ajustez vos préférences.
Chrome (Desktop)
  1. Cliquez sur l'icône représentant un cadenas dans la barre d'adresse..
  2. Select Paramètres du site.
  3. Find Notifications et ajustez vos préférences.