Myrax docs

Status and support

When something feels broken there are two questions with different answers: is the server up, and is my machine set up. This page is about telling them apart.

When something feels broken, there are two questions and they have different answers: is the server up, and is my machine set up. This page is about telling them apart before you spend an hour on the wrong one.

The status page

The status page asks the running server on every request. It is not a hand-written banner that someone forgets to update. It reports three components: the web app, the database, and mail delivery.

What it can see

  • That the app answered.
  • That the database was readable in the same request.
  • Whether a mail transport is configured for sign-in codes.
  • The age of the running process, which resets on every deploy.

What it cannot see

This is the honest limit of any self-check: it runs on the server, so it knows nothing about the route between you and it. It cannot see your DNS, your network, a proxy in between, or a provider outage outside this machine. If the status page loads but the app does not, the problem is between you and the server.

Telling the two failures apart

What you seeWhere to look
The site does not load at allCheck status from another network. If it loads there, the problem is your side.
The site loads, a build does nothingThe Connector daemon is not running, or the computer is offline. Run doctor and check the device row.
A build fails in secondsA provider problem: missing credential or empty balance. See Providers and keys.
Sign-in codes never arriveMail delivery. The status page shows whether a transport is configured; check spam, then the address itself.

Who answers

The contact page lists the addresses that are read: support, security, privacy and abuse. One person reads them, so a specific subject line and a project name get a faster reply than a general question.

What to include in a report

  • The build name and roughly when it ran.
  • The state it reached (awaiting-agent, running, failed) and the failed check with the value it measured.
  • The output of myrax-connector doctor, with keys and tokens removed.
  • What you expected instead.

The states a build passes through are listed in How a build works, and the check names in the browser gate.