Troubleshoot setup and connection¶

Fixes for the problems people meet most often when connecting an execution host.

The install command fails in Command Prompt¶

The Windows install command uses irm and iex, which are PowerShell commands. Run it in Windows PowerShell instead of Command Prompt (cmd.exe).

`revelion` isn't recognised on Windows¶

The installer adds %LOCALAPPDATA%\Revelion to your user PATH, and to the PowerShell window it ran in. Other windows that were already open keep their old PATH. Open a new PowerShell window and try again.

`Status: NOT CONFIGURED`¶

revelion status shows this when the daemon has no configuration file, which means no token has been saved. Authenticate, then start the daemon:

Terminal

revelion auth YOUR_DAEMON_TOKEN
revelion start

Starting without a configuration fails with Config not found. Run 'revelion auth <token>' first. Your token is the value in the install command shown in the Install Daemon panel on the Daemons page.

Docker isn't found or isn't running¶

The daemon needs Docker to run a mission's tools. The installer checks for Docker and warns you if it can't use it.

If Docker isn't installed, follow Docker's installation guide.
If it's installed but not running, start Docker Desktop on Windows or macOS, or the Docker service on Linux.
On Linux, if Docker is running but your user account can't use it, work through Docker's post-installation steps with whoever manages the machine. Adding a user to the docker group gives that user root-level privileges on the host, so it's a decision for the machine's administrator.

The daemon isn't shown as online¶

revelion status only reads the configuration file, so it can't tell you whether the daemon is connected. Work through these in order:

Is the daemon running? It runs in the foreground. If the window that started it was closed, run revelion start again.
Is the token right? Copy the install command from the Install Daemon panel again and re-run it, or run revelion auth with the token it contains.
Can the machine connect out? The daemon needs outbound HTTPS on port 443.
Is a proxy inspecting TLS? See the next section.

A proxy or TLS inspection blocks the connection¶

Some corporate proxies intercept TLS connections, which can break the daemon's connection to Revelion. To find the address the daemon connects to, run:

Terminal

revelion status

The Brain line shows the address. Ask your network team to allow connections to it and to exclude it from TLS inspection. Don't work around the problem by turning off certificate checks on the machine.

"No daemon connected" when launching a mission¶

The mission wizard shows No daemon connected. Install and start the Revelion daemon first. when no execution host is online. Start the daemon, check that it's shown as Online on the Daemons page, and launch again.

The first mission is slow to start¶

The first time the daemon needs its tool container image, Docker downloads it. Later missions reuse the downloaded image.

`revelion install-service` isn't recognised¶

There's no such command. The daemon accepts auth, start, status and version, and runs in the foreground in the window that started it.

Reporting a problem¶

Include the output of revelion version and revelion status. revelion status masks your token, showing only its first and last four characters.