> ## Documentation Index
> Fetch the complete documentation index at: https://docs.levelrail.com/llms.txt
> Use this file to discover all available pages before exploring further.

# First 15 minutes

> A checklist for a new server: install, open the setup link, turn on HTTPS, deploy an app and take your first backup. Each step links to the full page.

This is a checklist, not a full guide. Do the steps in order. Each one says what you should see and where to look if it fails. You need a fresh Linux server with root access and ports 80 and 443 open in the cloud firewall.

## 1. Install

```bash theme={"dark"}
curl -fsSL https://levelrail.com/install.sh | sudo sh
```

You should see a dashboard link with a one-time setup token. If it fails, see [Installing Levelrail](https://docs.levelrail.com/installing.md). If the ports are not open yet, see [Cloud firewall rules](https://docs.levelrail.com/cloud-firewall-rules.md).

## 2. Open the setup link

Port 8080 should stay closed to the internet, so tunnel it first. On your laptop:

```bash theme={"dark"}
ssh -L 8080:127.0.0.1:8080 <user>@<server-ip>
```

Open the link from the installer output with `localhost` as the host, and choose a password. You should land on the first-run screen. If the link is lost or rejected, see [Getting started](https://docs.levelrail.com/getting-started.md#sign-in-and-deploy-your-first-app) or print the token again:

```bash theme={"dark"}
sudo APP_DATA_DIR=/var/lib/levelrail-data levelrail setup-token
```

Why 8080 stays closed: [Dashboard port 8080](https://docs.levelrail.com/installing.md#dashboard-port-8080).

## 3. Turn on HTTPS

On the first-run screen, press **Enable HTTPS**. No DNS record is needed. You get an address like `203-0-113-10.sslip.io` with a Let's Encrypt certificate. From a terminal:

```bash theme={"dark"}
levelrail-cli settings ingress https enable --wait 2m
levelrail-cli settings ingress https status
```

After this, open the dashboard on the https address and sign-in over plain HTTP stops working. If it fails, see [Zero to HTTPS](https://docs.levelrail.com/zero-to-https.md#5-when-it-does-not-work).

## 4. Deploy an app

On the same screen, deploy a sample app or pick a template. You can also paste a repository URL under **New app**. The screen waits until the app is healthy and ends on its live link. If the build fails, the screen shows a diagnosis and a link to the logs. More options: [Getting started](https://docs.levelrail.com/getting-started.md#deploy-your-first-app) and [Templates](https://docs.levelrail.com/templates-and-registry.md).

## 5. Take your first backup

Back up `master.key` first. Without it, stored secrets cannot be read after a restore. Then take a snapshot of the control plane database:

```bash theme={"dark"}
levelrail-cli control-plane-backups create
levelrail-cli control-plane-backups list
```

You should see one snapshot in the list. It lives on the server's disk, so it does not protect you if the server is lost. The rest of the path, including an off-server target, is in [First backup in 5 minutes](https://docs.levelrail.com/backups-and-storage.md#first-backup-in-5-minutes).

## 6. Check the server

```bash theme={"dark"}
levelrail-cli doctor
```

Read any `fail` rows and fix them. A `warn` on external reachability is a hint, not proof: test from another machine. See [Doctor](https://docs.levelrail.com/doctor.md).

## What next

* [Zero to HTTPS](https://docs.levelrail.com/zero-to-https.md): move from the test address to your own domain.
* [Go live checklist](https://docs.levelrail.com/go-live.md): point a domain at an app.
* [Domains and ingress](https://docs.levelrail.com/domains-and-ingress.md): how names and certificates work.
* [Backups and storage](https://docs.levelrail.com/backups-and-storage.md): schedules and restores.

## Related

* [Installing Levelrail](https://docs.levelrail.com/installing.md)
* [Getting started](https://docs.levelrail.com/getting-started.md)
* [Cloud firewall rules](https://docs.levelrail.com/cloud-firewall-rules.md)
* [Troubleshooting](https://docs.levelrail.com/troubleshooting.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.