TOWERBY CETMIX
← Hangar / server_template_jet_base

Hetzner Cloud Server Template for Tower Jets

Provision an Ubuntu server on Hetzner Cloud and configure it in Cetmix Tower with SSH checks, Jet path defaults and weekly package updates.

↓ Download↓ 1 download

Summary

Category
Server Templates
Tags
HostingSystem
Authors
Cetmix OÜ
License
AGPL-3
Version
1.0.0
Call sign
server_template_jet_base

This snippet imports the Jet Base Server Template. Its defaults request an Ubuntu 24.04 CX23 server with public IPv4 in Hetzner's fsn1 location. The template defines root SSH access on port 22 using the Cetmix Cloud SSH key. It also sets the Tower root, Jet and template paths, Dockerfile location, Docker network name (tower), and the Cloudflare DNS provider preference used by compatible Jet templates.

Configure and provision

  1. Import the YAML into Cetmix Tower. Set the hetzner_api_token secret to a Hetzner Cloud API token for the target project. Load the cetmix_cloud SSH key into Tower and register its matching public key in that Hetzner project under cetmix-cloud. The provisioning command derives the Hetzner key name from the Tower key reference by replacing underscores with hyphens.
  2. Review the location, server type and Ubuntu image variables, then create a server from Jet Base. The creation plan checks the Tower and Jet path variables, creates the cloud server when no hetzner_server_id is set, saves the server ID and IPv4 address, and waits for Hetzner to report the server as running.
  3. The plan checks SSH connectivity, fetches and stores the host key if needed, and confirms that the key is present when verification is enabled. Install Docker and the desired Jet templates separately on the provisioned host.

Operate and troubleshoot

The template attaches a weekly apt package update and upgrade task, and provides server log views for Docker containers and their memory usage once Docker is available. If provisioning fails, check the creation Flight Plan log for the failing step. For Hetzner errors, verify the Cloud API token, selected server options and SSH key registration. For SSH failures, verify that Tower can reach port 22 at the assigned address and that the private key matches the registered public key.