Deploy OpenClaw to production servers with openclaw-ansible -- an automated installer with security-first architecture.
Prerequisites
| Requirement | Details |
|---|---|
| OS | Debian 11+ or Ubuntu 20.04+ |
| Access | Root or sudo privileges |
| Network | Internet connection for package installation |
| Ansible | 2.14+ (installed automatically by the quick-start script) |
What you get
- Firewall-first security -- UFW + Docker isolation (only SSH + Tailscale accessible)
- Tailscale VPN -- secure remote access without exposing services publicly
- Docker -- isolated sandbox containers, localhost-only bindings
- Defense in depth -- 4-layer security architecture
- Systemd integration -- auto-start on boot with hardening
- One-command setup -- complete deployment in minutes
Quick start
One-command install:
curl -fsSL https://raw.githubusercontent.com/openclaw/openclaw-ansible/main/install.sh | bash
What gets installed
The Ansible playbook installs and configures:
- Tailscale -- mesh VPN for secure remote access
- UFW firewall -- SSH + Tailscale ports only
- Docker CE + Compose V2 -- for the default agent sandbox backend
- Node.js 24 + pnpm -- runtime dependencies (Node 22 LTS, currently
22.16+, remains supported) - OpenClaw -- host-based, not containerized
- Systemd service -- auto-start with security hardening
Post-Install Setup
Quick commands
# Check service status
sudo systemctl status openclaw
# View live logs
sudo journalctl -u openclaw -f
# Restart gateway
sudo systemctl restart openclaw
# Provider login (run as openclaw user)
sudo -i -u openclaw
openclaw channels login
Security architecture
The deployment uses a 4-layer defense model:
- Firewall (UFW) -- only SSH (22) + Tailscale (41641/udp) exposed publicly
- VPN (Tailscale) -- gateway accessible only via VPN mesh
- Docker isolation -- DOCKER-USER iptables chain prevents external port exposure
- Systemd hardening -- NoNewPrivileges, PrivateTmp, unprivileged user
To verify your external attack surface:
nmap -p- YOUR_SERVER_IP
Only port 22 (SSH) should be open. All other services (gateway, Docker) are locked down.
Docker is installed for agent sandboxes (isolated tool execution), not for running the gateway itself. See [Multi-Agent Sandbox and Tools](/docs/openclaw-docs/tools/multi-agent-sandbox-tools for sandbox configuration.
Manual installation
If you prefer manual control over the automation:
Alternatively, run directly and then manually execute the setup script afterward:
```bash
ansible-playbook playbook.yml --ask-become-pass
# Then run: /tmp/openclaw-setup.sh
```
Updating
The Ansible installer sets up OpenClaw for manual updates. See [Updating](/docs/openclaw-docs/install/updating for the standard update flow.
To re-run the Ansible playbook (for example, for configuration changes):
cd openclaw-ansible
./run-playbook.sh
This is idempotent and safe to run multiple times.
Troubleshooting
# Verify permissions
sudo ls -la /opt/openclaw
# Test manual start
sudo -i -u openclaw
cd ~/openclaw
openclaw gateway run
```
# Check sandbox image
sudo docker images | grep openclaw-sandbox
# Build sandbox image if missing (requires source checkout)
cd /opt/openclaw/openclaw
sudo -u openclaw ./scripts/sandbox-setup.sh
# For npm installs without a source checkout, see
# https://docs.openclaw.ai/gateway/sandboxing#images-and-setup
```
Advanced configuration
For detailed security architecture and troubleshooting, see the openclaw-ansible repo:
Related
- openclaw-ansible -- full deployment guide
- [Docker](/docs/openclaw-docs/install/docker -- containerized gateway setup
- [Sandboxing](/docs/openclaw-docs/gateway/sandboxing -- agent sandbox configuration
- [Multi-Agent Sandbox and Tools](/docs/openclaw-docs/tools/multi-agent-sandbox-tools -- per-agent isolation