Provision a new or existing Ubuntu server.
ServerChirp supports provider-created servers, managed SSH installation, and self-run bootstrap installation. All three paths converge on the same tested server stack and outbound agent.
Use a clean, supported Ubuntu 22.04, 24.04, or 26.04 LTS server with root access, working DNS resolution, and outbound HTTPS and agent-broker connectivity. The machine needs enough free disk and memory for package installation.
Existing services that already bind ports 80, 443, or managed database ports can conflict with provisioning. Move important data off the server before allowing ServerChirp to replace system configuration.
Managed SSH accepts a one-time root password, connects to the server, and runs the installer. The password is encrypted in transit, used only for provisioning, and permanently deleted afterward. ServerChirp streams the installation stages to the dashboard.
The bootstrap command mints a one-time agent-enrollment token each time it is requested. Treat the entire command as a credential until it has been used or expired.
Connect to the target machine as root and run the generated script exactly as shown in ServerChirp. Do not edit it or reuse a previously loaded command.
Do not paste a bootstrap command into a public issue, chat room, or CI log.
The installer validates the operating system, configures package sources, installs the selected stack, applies security defaults, installs the agent, and verifies that the agent can connect. The dashboard shows each stage independently so a retry can start from a known state.
Open the failed stage and preserve its output. Check the following before retrying:
If the installer made partial changes, use the guided retry instead of repeatedly running an old bootstrap command.
