status
The blocklet server status command displays the current operational status of your Blocklet Server and a summary of all installed blocklets. It is a primary tool for monitoring the health of your server instance and is often the first step in diagnosing issues.
This command is part of the server command set. For more server management commands, see the server documentation.
Usage#
To check the status, run the following command from your terminal:
blocklet server statusOptions#
Option | Description |
|---|---|
| Forces the display of intranet access URLs, even if public URLs are available. This is useful when you need to access the server from the local network specifically. |
Output Breakdown#
The command's output provides a comprehensive overview broken down into several parts:
1. Server Information#
This section displays high-level details about the Blocklet Server daemon:
- Blocklet Server status: Shows the current state of the server (e.g.,
Running,Stopped,Error) and its uptime if it is running. - Blocklet Server mode: Indicates the operational mode, such as
ProductionorDevelopment. - Blocklet Server Data Directory: The absolute file path to the directory where all server data is stored.
2. Blocklets Status Table#
If you have blocklets installed, their status is presented in a table with the following columns:
Column | Description |
|---|---|
| The title of the blocklet as defined in its metadata. |
| The current runtime status of the blocklet (e.g., |
| The public URL to access the blocklet. |
If no blocklets are installed, a warning message No blocklets installed yet. is displayed instead.
3. Access URLs#
When the server is in a running state, this section lists the URLs you can use to access the Blocklet Server dashboard.
Example Output#
Here is an example of what you might see after running the command:
$ blocklet server status
Blocklet Server status: Running (2 hours)
Blocklet Server mode: Production
Blocklet Server Data Directory: /home/user/.abtnode
Blocklets Status:
┌──────────────────────────────┬───────────────┬────────────────────────────────────────────────────────────────────┐
│ Name │ Status │ URL │
├──────────────────────────────┼───────────────┼────────────────────────────────────────────────────────────────────┤
│ My First Blocklet │ running │ https://z2qa15e3...a1b2c3d4.did.abtnet.io │
├──────────────────────────────┼───────────────┼────────────────────────────────────────────────────────────────────┤
│ Another Cool App │ stopped │ https://z2qb45f6...e5f6g7h8.did.abtnet.io │
└──────────────────────────────┴───────────────┴────────────────────────────────────────────────────────────────────┘
You can access your blocklet server with either of the following URLs:
- Mainnet: https://z2q...d.did.abtnet.io
- Local: http://192.168.1.100:8089If the server is not running, the output will be much simpler:
$ blocklet server status
Blocklet Server is not startedAfter checking the status, you may need to take further action. If the server is stopped, you can start it with [start](./commands-server-start.md). If a blocklet is in an error state, you might want to inspect its activity using the [logs](./commands-server-logs.md) command.