Skip to content
>MAAD

/// MAAD TERMINAL

MAAD Connect troubleshooting.

Find the part that failed, then follow its section.

A MAAD Connect connection goes through four parts, in this order:

  1. This device reaches MAAD Connect over the internet.
  2. MAAD Connect checks your sign-in and the host's link.
  3. The host's tunnel (cloudflared on the host) carries the request to the host.
  4. MAAD Terminal on the host answers.

When a connection fails, open Settings > Environments, find the environment, and select Details. The first part marked as failed is the cause. Find its section below.

To see the host's side, run maad connect status on the host, or open Settings > Sharing & access on the host. Both check the host's MAAD Connect address from the host, and say why it fails. maad connect runs the same check when it finishes setup. This check cannot test another device's network. For a problem on one device, use Details on that device.

The host's tunnel is offline

MAAD Connect could not reach the host's tunnel. This means one of these:

  • The host is asleep, turned off, or offline.
  • MAAD Terminal is not running on the host.
  • The host's network blocks the tunnel. See Port 7844 is blocked on the host.

Fix:

  1. Make sure the host is awake and MAAD Terminal runs on it.
  2. On the host, run maad connect status. It names the problem on the host's side.
  3. If the host was offline for a long time, MAAD Connect removes its tunnel. Start MAAD Terminal on the host and update it to the latest version. It gets a new tunnel.

Port 7844 is blocked on the host

The tunnel on the host connects out to Cloudflare on port 7844, with TCP and UDP. Both tunnel protocols (QUIC and HTTP/2) use this port. When the host's network blocks it, the tunnel cannot start, but normal web traffic still works. The host looks online, so this problem is easy to miss.

Common causes:

  • A Tailscale exit node on the host. All of the host's internet traffic goes through the exit node, and that network blocks port 7844. Turn off the exit node on the host with tailscale set --exit-node=, or allow outbound port 7844 on the exit node's network.
  • A VPN on the host. Work VPNs often block unknown ports. Ask for port 7844 to be allowed, or use a direct route instead (see below).
  • A firewall or strict network. Allow outbound TCP and UDP port 7844.

If you cannot unblock the port, you can connect without MAAD Connect. When the host and this device are on the same Tailscale network, add the host's Tailscale address as a direct route. See Reach one machine several ways.

The tunnel works, but MAAD Terminal does not answer

The host's tunnel is up, but it cannot reach MAAD Terminal on the host. Common causes:

  • MAAD Terminal on the host stopped, crashed, or is still starting.
  • MAAD Terminal restarted on a different port, for example after an update, and the tunnel still points at the old port.
  • The server binds only one network address with MAAD_HOST. The tunnel sends requests to 127.0.0.1, so the server must also listen there.

Fix: restart MAAD Terminal on the host. For the background service, run maad service restart. Then run maad connect status on the host.

The MAAD Connect address does not resolve or answer

The host's MAAD Connect address did not resolve, refused the connection, failed a secure (TLS) connection, or did not answer in time.

Fix:

  1. Make sure the host is awake and online.
  2. On the host, run maad connect status.
  3. If the check fails only on the host, check the host's DNS, VPN, or proxy.

This device can't reach MAAD Connect

The problem is on this device's network, not on the host. This device could not reach MAAD Connect, or it reached MAAD Connect but not the host's tunnel address.

Fix:

  1. Check this device's internet connection. On a captive or dead Wi-Fi network, the device can look online but cannot reach anything.
  2. A VPN, firewall, ad blocker, or DNS filter on this device can block MAAD Connect. Turn it off for a moment to test.
  3. On iPhone, Connectivity Assist in the Wi-Fi settings can break MAAD Connect. Turn it off to test.
  4. Try another network, or add a direct route to the host, such as its Tailscale address. See Reach one machine several ways.

This device's MAAD Connect sign-in is not ready yet, or MAAD Connect does not have an active link between your account and the host.

  • The host is linked to a different account. Sign in to the same MAAD Connect account on this device and on the host. On the host, run maad connect logout, then maad connect.
  • MAAD Connect is off on the host, or the host only publishes agent activity. On the host, open Settings > Sharing & access and turn MAAD Connect on, or run maad connect.
  • The host was linked, but the server did not apply the link yet. Restart the server on the host: quit and reopen the MAAD Terminal desktop app, run maad service restart, or stop maad serve and run it again.
  • This device's sign-in expired, or the host no longer accepts this device. Sign out of MAAD Connect and sign in again.
  • Your MAAD Society Operator membership is not active. MAAD Connect refuses sign-ins without it. Check your membership at maadsociety.com/terminal, then sign in again.
  • This device is still loading its MAAD Connect sign-in. Wait a moment; MAAD Terminal retries on its own. If it keeps waiting, reload or restart MAAD Terminal on this device.
  • Your account reached its tunnel limit. Remove an environment you do not use from your MAAD Terminal account's MAAD Connect page, then restart MAAD Terminal on the host.

The clock is off

MAAD Connect signs requests with short-lived proofs. When the clock on this device or the host is a few minutes wrong, MAAD Connect rejects them. Turn on automatic date and time on both devices, then retry.

The host runs an older MAAD Terminal

This app needs a newer MAAD Terminal on the host. Update MAAD Terminal on the host. See Updating MAAD Terminal.

MAAD Connect returned an error

| Error | Fix | | --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | | environment_link_limit_exceeded or managed tunnel limit | Remove an unused environment, then restart MAAD Terminal on the host. | | auth_invalid or invalid_bearer | Run maad connect login. If credentials were revoked, run maad connect logout, then maad connect again. Restart the server after signing in. | | Expired or invalid link proof | Check the host's date and time, update MAAD Terminal, then restart it. | | HTTP 403 without a recognized error | Check relay access, proxies, and firewall rules. Keep any Cloudflare Ray ID for a bug report. | | HTTP 408, 429, or 5xx | Wait a few minutes. MAAD Terminal retries temporary failures on its own. |

After you fix a permanent rejection, restart the host's server with maad service restart. For a foreground server, stop it and run maad serve again.

If MAAD Terminal on the host disappears when SSH closes, see background-service troubleshooting.

Report a problem

If none of this helps, send a report through maadsociety.com/support. Include:

  • The text from Copy diagnostics in the environment's Details.
  • The output of maad connect status on the host.
  • The trace ID, if one is shown.
  • If the tunnel dropped earlier, the host's tunnel log, relay-client.ndjson in the logs folder (~/.maad/userdata/logs by default). It records when the tunnel connected, warned, exited, and restarted, with the tunnel token removed.