let5see/clawdbot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: improve Hetzner 24/7 VPS guide

Browse Source
This commit is contained in:
Peter Steinberger
2026-01-10 01:43:28 +01:00
parent 60bd65dfac
commit 626b085c85
1 changed files with 31 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

35
docs/platforms/hetzner.md
View File

@@ -1,6 +1,7 @@
--- ---
summary: "Run Clawdbot Gateway on Hetzner (Docker + VPS) with durable state and baked-in binaries" summary: "Run Clawdbot Gateway 24/7 on a cheap Hetzner VPS (Docker) with durable state and baked-in binaries"
read_when: read_when:
- You want Clawdbot running 24/7 on a cloud VPS (not your laptop)
- You want a production-grade, always-on Gateway on your own VPS - You want a production-grade, always-on Gateway on your own VPS
- You want full control over persistence, binaries, and restart behavior - You want full control over persistence, binaries, and restart behavior
- You are running Clawdbot in Docker on Hetzner or a similar provider - You are running Clawdbot in Docker on Hetzner or a similar provider
@@ -11,6 +12,17 @@ read_when:
## Goal ## Goal
Run a persistent Clawdbot Gateway on a Hetzner VPS using Docker, with durable state, baked-in binaries, and safe restart behavior. Run a persistent Clawdbot Gateway on a Hetzner VPS using Docker, with durable state, baked-in binaries, and safe restart behavior.
If you want “Clawdbot 24/7 for ~$5”, this is the simplest reliable setup.
Hetzner pricing changes; pick the smallest Debian/Ubuntu VPS and scale up if you hit OOMs.
## What are we doing (simple terms)?
- Rent a small Linux server (Hetzner VPS)
- Install Docker (isolated app runtime)
- Start the Clawdbot Gateway in Docker
- Persist `~/.clawdbot` + `~/clawd` on the host (survives restarts/rebuilds)
- Access the Control UI from your laptop via an SSH tunnel
The Gateway can be accessed via: The Gateway can be accessed via:
- SSH port forwarding from your laptop - SSH port forwarding from your laptop
- Direct port exposure if you manage firewalling and tokens yourself - Direct port exposure if you manage firewalling and tokens yourself
@@ -38,6 +50,8 @@ For the generic Docker flow, see [Docker](/install/docker).
- Hetzner VPS with root access - Hetzner VPS with root access
- SSH access from your laptop - SSH access from your laptop
- Basic comfort with SSH + copy/paste
- ~20 minutes
- Docker and Docker Compose - Docker and Docker Compose
- Model auth credentials - Model auth credentials
- Optional provider credentials - Optional provider credentials
@@ -124,6 +138,12 @@ GOG_KEYRING_PASSWORD=change-me-now
XDG_CONFIG_HOME=/home/node/.clawdbot XDG_CONFIG_HOME=/home/node/.clawdbot
``` ```
Generate strong secrets:
```bash
openssl rand -hex 32
```
**Do not commit this file.** **Do not commit this file.**
--- ---
@@ -155,9 +175,14 @@ services:
- ${CLAWDBOT_CONFIG_DIR}:/home/node/.clawdbot - ${CLAWDBOT_CONFIG_DIR}:/home/node/.clawdbot
- ${CLAWDBOT_WORKSPACE_DIR}:/home/node/clawd - ${CLAWDBOT_WORKSPACE_DIR}:/home/node/clawd
ports: ports:
- "${CLAWDBOT_GATEWAY_PORT}:18789" # Recommended: keep the Gateway loopback-only on the VPS; access via SSH tunnel.
- "${CLAWDBOT_BRIDGE_PORT}:18790" # To expose it publicly, remove the `127.0.0.1:` prefix and firewall accordingly.
- "18793:18793" - "127.0.0.1:${CLAWDBOT_GATEWAY_PORT}:18789"
# Optional: only if you run iOS/Android nodes against this VPS.
# If you expose these publicly, read /gateway/security and firewall accordingly.
# - "${CLAWDBOT_BRIDGE_PORT}:18790"
# - "18793:18793"
command: command:
[ [
"node", "node",
@@ -227,6 +252,8 @@ RUN pnpm build
RUN pnpm ui:install RUN pnpm ui:install
RUN pnpm ui:build RUN pnpm ui:build
ENV NODE_ENV=production
CMD ["node","dist/index.js"] CMD ["node","dist/index.js"]
``` ```