Connect a server

Add a server to your fleet — automatic enrollment over SSH, or manual install with a token.

There are two ways to bring a server under CentralHost. Both end the same way: the agent enrolls, gets a per-host control token, and the server shows up in your dashboard.

Option A — automatic (over SSH)

Let CentralHost install and enroll the agent for you. This is the fastest path.

1. In the dashboard, click Add server.
2. Enter the server’s address and SSH credentials (a key is recommended over a password).
3. CentralHost connects over SSH, installs the agent package and enrolls it automatically.

The SSH credentials are used once to bootstrap the agent — ongoing access flows through the control plane, not SSH.

Option B — manual (with an enrollment token)

Prefer to run the install yourself? Generate a token instead.

1. In the dashboard, click Add server → Install manually.
2. Copy the enrollment token.
3. Run the agent installer on the server with that token:

curl -fsSL https://get.centralhost.sh/install.sh | sudo sh -s -- --token <ENROLLMENT_TOKEN>

Enrollment tokens are single-use and short-lived. If a token expires before you use it, generate a new one from the dashboard.

Verify the connection

Once enrolled, the server appears in your fleet with live status. You can confirm from the server itself:

systemctl status centralhost-agent
journalctl -u centralhost-agent -n 20

A healthy agent logs a successful connection to the control plane. From there you can open the browser SSH terminal, run the AI Assistant, and review the server’s security posture.

Troubleshooting

• Server doesn’t appear — check outbound HTTPS is allowed; the agent needs to reach the control plane.
• active (running) but no connection — inspect journalctl -u centralhost-agent for the enrollment result; an expired token is the most common cause.