Deploy Cresdock — the simple setup guide
Cresdock installs onto a server you own with a single command. This guide takes a non-technical admin from nothing to a running panel: which server to get, what specs you need, and exactly what happens during install. Plan for about 15 minutes.
1.What you need
Three things — no coding and no Docker knowledge:
- A server
A rented cloud server (a “VPS”) or a spare computer at home. We’ll pick the right one in the next step.
- About 15 minutes
And the ability to copy-and-paste one command.
- A domain name (optional, but recommended)
Something like panel.yourname.com. It gives you proper padlock—HTTPS and tidy links. You can skip it for a quick test.
2.Pick a server — OS and specs
Operating system: use Ubuntu 22.04 (or newer) or Debian 12 (or newer). These are the two we test on, both are free, and every cloud provider offers them as a one-click choice when you create a server. Please don’t use Windows or macOS — Cresdock runs on Linux.
How much power? Match this to how many people will use it:
| Minimum | Comfortable | What it affects | |
|---|---|---|---|
| CPU | 2 cores | 4+ cores | More people and more running apps want more cores. |
| Memory (RAM) | 4 GB | 8–16 GB | Each active app uses some; RAM is the first thing to run low. |
| Disk | ~30 GB for the system | a big data disk | Your files (downloads, media) live here — size it for what you’ll actually store, e.g. 1–4 TB. |
Where to get one: any major provider works — Hetzner, DigitalOcean, OVH, Contabo and others. When creating the server, choose Ubuntu 22.04, at least 2 CPU / 4 GB RAM, and add storage for your files. A home mini-PC running Ubuntu works too.
3.Point a domain at your server (recommended)
A domain gives you real, trusted HTTPS and clean web addresses. At your domain registrar (where you bought the name), add two records that point at your server’s IP address:
| Type | Name | Points to |
|---|---|---|
| A | panel.yourname.com | your server’s IP |
| A | *.panel.yourname.com (a “wildcard”) | your server’s IP |
The wildcard (the one starting with *.) matters: streaming apps like Plex and Jellyfin get their own web address, and this makes those work. Also open ports 80 and 443 on the server (most cloud servers have these open already).
4.Run the installer
Connect to your server (your provider shows you how — it’s usually a “Console” button or an ssh command), then paste this one line and press Enter:
That’s the entire install. It will ask you one or two simple questions (your domain, and whether to get real HTTPS certificates) — press Enter to accept the sensible default each time.
Power users: install without any questions
Provide everything up front to run unattended:
--domain panel.yourname.com \
--email you@example.com \
--tls letsencrypt \
--data-dir /mnt/storage
| Option | What it does |
|---|---|
--domain | Your panel’s domain (needs the two DNS records above). |
--tls | letsencrypt = automatic real certificates (needs --email + public DNS); selfsigned = local test cert; none = handle HTTPS yourself. |
--data-dir | Where all files live — point this at your biggest disk. |
--routing | path (default) or subdomain for app addresses. |
5.What to expect during install
The installer runs on its own — here’s what it’s doing so nothing looks alarming:
- Installs Docker
If your server doesn’t already have it, the installer adds it for you.
- Generates your passwords & secrets
Everything is created fresh and unique to your box — nothing is shared or preset.
- Sets up the panel and its private networking
Including isolating each future user so they can never see each other’s apps.
- Requests HTTPS certificates
If you chose a real domain, it gets trusted certificates automatically.
- Starts everything up
A few minutes later the panel is live.
6.First login
- Open your panel
Go to
https://panel.yourname.com/(or the local address the installer printed if you skipped the domain). - Sign in
Use the admin username and password from the end of the install.
- Secure your account
Set your email, change to a passphrase you’ll remember, and turn on two-factor authentication under Profile → Security. Recommended, since this account controls the whole box.
7.Use it solo, or add people
Out of the box your server runs one user — perfect for a personal setup. Install apps and you’re done.
Want to share it with family, friends, or paying customers? Each person gets their own private, isolated space:
- Go to Users → Add user
Enter their email to send an invite link (they set their own password).
- Pick their plan
Set how much disk, how many apps, and their speed limits — right there on the form.
- They take it from there
Point them at the user guide for installing and using their apps.
8.If something goes wrong
| You see… | What’s happening & the fix |
|---|---|
| Browser warns the site “isn’t secure” | You’re in test mode with a local certificate. Add a real domain and re-run with real certificates for a trusted padlock. |
| A streaming app “won’t load” | Almost always a missing wildcard DNS record (*.yourname.com). Add it, then rebuild the app. |
| HTTPS certificate didn’t come through | Make sure ports 80 and 443 are open and both DNS records point at the server, then re-run. |
| Ran out of disk space | You likely installed onto the small system disk. Re-run the installer with --data-dir pointing at your big disk. |