Quickstart

What you need

A server

Ubuntu 24.04 LTS on x86_64, freshly installed, with root over SSH. 1 GB of RAM and 10 GB of free disk. Ports 80, 443 and 7443 free. Outbound HTTPS working. The installer refuses a server that already carries another panel, Apache, or an nginx or MariaDB it did not configure. Requirements

A domain

One you can add an A record to. Let's Encrypt will not issue a certificate until the name points at the server.

Nothing else

No account at my.klyrn.com and no licence key. With no key the server runs the Free edition: one server, five sites, everything except cPanel and DirectAdmin migration, staging and resellers.

The eight steps

1. Install As root. The bootstrap verifies the download's SHA-256 and the manifest's signature, then runs eleven stages that each verify their own result. The first clean run on a 3-vCPU, 5.9 GB VPS took 53 seconds.
   curl -fsSL https://get.klyrn.com | sudo bash
   Install
2. Create the first administrator The installer's last lines are the panel address and a one-time setup token. Open https://<your-ip>:7443 and accept the certificate warning. The panel is self-signed until step 4. Paste the token and create the account. First setup
3. Turn on two-factor sign-in Do it now. Account, then Two-factor sign-in: scan the code with any TOTP app, confirm one code, save the eight recovery codes. They are shown once. Signing in
4. Give the panel a hostname Point panel.example.com at the server, then run klyrn panel hostname panel.example.com. A real certificate replaces the self-signed one and the browser warning stops. Panel hostname
5. Point your domain at the server Add an A record for the name, and for www if you use it, wherever your zone is held. Or make this server the nameserver. If Cloudflare already holds the zone, connect it once and klyrn dns point example.com writes the records. DNS
6. Create the site One button, or one command. One job creates the account, its Unix user, the PHP-FPM pool, the nginx server block, the database, WordPress and the certificate.
   klyrn site create example.com --type wordpress --admin-email you@example.com
   Sites
7. Let HTTPS arrive The certificate is requested when the site is created and renewed 30 days before expiry. If the name does not resolve here yet, the site is served over HTTP and the certificate is retried every ten minutes. klyrn dns check example.com shows what the name resolves to now. Certificates
8. Set a backup schedule A backup counts only after the archive is listed back and every checksum in its manifest matches. Add an off-site destination too, so the site survives a lost disk.
   klyrn backup schedule example.com daily --keep 7
   Backups

Fifteen minutes is the hands-on time. The install is measured at 53 seconds and the panel steps take a couple of minutes each. A certificate cannot be issued until the name resolves to this server, and your DNS provider decides how long that takes.

A licence key, if you want one

The server already runs the Free edition. A Free key from my.klyrn.com adds the server to your account there, where a paid licence such as Pro is activated. If licensing is unreachable, sites, backups and renewals carry on.

klyrn license activate <key>
klyrn license status

Activating a licence

Where to go next

• Run WordPress properlyHealth signals, four hardening actions, staging, and an update policy that backs up first.
• Move a site that exists somewhere elseA cPanel or DirectAdmin backup, or any server over SSH. Nothing is written until you have read the plan.
• Host customersAccounts, limits, resellers, backups per site, suspension and deletion.
• When something breaksStart from the symptom and get to the command that names the cause.