Tutorial: First day on Aux Server

Goal: Log into aux, confirm the host is healthy, and connect live state to the right docs section so you can operate without guessing.

Time: ~20 minutes
Level: Beginner (SSH + basic Linux)

Prerequisites

• SSH access as ty to 147.93.186.68 (alias aux / aux-serv if configured)
• Your ED25519 key authorized on the host
• This documentation site open in a browser

1. Connect

ssh ty@147.93.186.68
# or: ssh aux

You should land in /home/ty without a password prompt.

2. Confirm identity and load

hostnamectl
uptime
free -h
df -h /

Expect hostname auxserver-prod, Ubuntu 24.04, and disk usage well under capacity (historically single-digit % on root). Compare numbers to Quick facts and Hardware — treat the live host as authoritative if they disagree.

3. Check edge services

systemctl is-active caddy docker fail2ban ssh
ss -lntp | egrep ':(22|80|443)\b'

Caddy, Docker, Fail2Ban, and SSH should be active. Only 22/80/443 should listen on public addresses for the application edge.

4. Inventory containers

docker ps --format 'table {{.Names}}\t{{.Status}}\t{{.Ports}}'

You should see Nextcloud, n8n, Radicale, Portainer, and the HeyPuter fleet (puter/nginx pairs). Details: Container inventory.

5. Hit a public HTTPS front door

From your laptop (not necessarily on aux):

curl -sI https://cloud.cadenceworks.tech | head -5
curl -sI https://dav.cadenceworks.tech | head -5

Expect HTTP/2 200 or an app redirect — not connection refused or TLS errors.

6. Know where to go next

If you need to…	Open
Understand why apps bind to localhost	System architecture
Look up a port or compose path	Reference
Fix something that is down	How-to guides
Learn the Puter fleet hands-on	HeyPuter tutorial

Success criteria

• [ ] Passwordless SSH as ty works
• [ ] caddy and docker are active
• [ ] docker ps lists core stacks
• [ ] At least one public HTTPS check returns a normal response
• [ ] You can name which docs section to use for facts vs incidents