Skip to content

Install a single node TAPPaaS system in Hetzner

In development, not ready: this is how it will work. Until then, use a single node at home.

One rented Hetzner dedicated server, installed from your Mac or Linux PC through Hetzner's rescue system. No USB stick and no local network are involved. The server keeps its own address; the firewall gets a second public address of its own, which is where you and the internet reach the site. What to order and where in Hetzner's Robot: Appendix G.

What you need

  • A Hetzner dedicated server (Robot or Server Auction): 32 GB of memory, NVMe disks of 0.5 TB or more (two equal disks become a mirror). Hetzner's cloud servers cannot run TAPPaaS.
  • An additional IPv4 address for the server, with a virtual MAC generated for it in Robot.
  • Rescue mode activated on the server with your SSH key, and the server reset into it.
  • A Mac or Linux PC with curl and wg (on a Mac: brew install wireguard-tools; on Debian or Ubuntu: sudo apt install curl wireguard-tools), the SSH key you gave the rescue system, and the WireGuard app.

1. Run the install

In an empty directory:

curl -fsSL "https://codeberg.org/TAPPaaS/TAPPaaS/raw/branch/main/src/foundation/cluster/bootstrap-tappaas.sh" -o bootstrap-tappaas.sh && chmod +x bootstrap-tappaas.sh
./bootstrap-tappaas.sh

Choose 6, install TAPPaaS on a rented server (Hetzner), and answer:

  • the server's address, the additional address and its virtual MAC;
  • your admin email and a root password;
  • the site's name and size small.

The script then works on its own, in about an hour:

  1. It makes your computer's WireGuard key (the private half stays on your computer).
  2. On the rescue system it builds the Proxmox installer and runs it on the server's disks, with the server's own address, then reboots the server into Proxmox.
  3. It runs the TAPPaaS install, with the firewall on its own address and MAC. The server's own address then takes ssh with a key only (yours, and the script's).
  4. It enrols your WireGuard key in the site's admin VPN and writes your WireGuard file, <site>.conf, next to the script.

It ends with the console's address and how to show its access token.

2. Connect

Import <site>.conf into the WireGuard app and turn the tunnel on. The console, the firewall and the server's management are reached through it; the server's own address answers ssh only.

3. Day 1 in the console

Open the console's address and enter the access token. Then, as at home:

  1. Finish the first node's setup: This machine alone; Boot pool only (or a pool on the second disk if the boot disks are not mirrored).
  2. Add more nodes: No more machines.
  3. The admin VPN is already done: your computer was enrolled by the install.
  4. Rest of foundation, then Status and health checks.

Backup needs a place off the server: a backup buddy, or a second server later. Growing into a cluster: Multi node TAPPaaS cluster in Hetzner.