Deploy openclaw.ai on Hostinger VPS
Deploy openclaw.ai on a Hostinger VPS with persistent Gateway service and private dashboard access.
Size for Your Workload
Choose at least 2 GB RAM for a smoother setup. Browser automation, more channels, and local models require additional memory and storage.
Check Hostinger VPS availability
Pricing and promotional discounts vary by region and term.
Get Started âđ Prerequisites
Create a Hostinger VPS
Log in to hPanel and set up your VPS:
- Go to VPS â Setup on your purchased VPS plan
- Select your preferred server location (US, Europe, Asia, South America)
- Under Operating System, choose Ubuntu 24.04 LTS 64-bit or a newer supported LTS release
- Set a strong Root Password
- Optionally, set a Hostname (e.g.,
openclaw-vps) - Click Continue to provision the server
SSH Key Setup
For better security, add your SSH public key in hPanel under VPS â Settings â SSH Keys after provisioning. Then disable password authentication.
Connect via SSH
Find your VPS IP address in hPanel under VPS â Information, then connect:
# Replace with your VPS IP from hPanel
ssh root@your-vps-ip
Alternatively, Hostinger provides a Browser terminal in hPanel â click VPS â Browser terminal if you can't use a local SSH client.
System Update & Dependencies
Update the package index and upgrade all installed packages:
sudo apt update && sudo apt upgrade -y
Install supported Node.js version
openclaw.ai requires Node.js 22.22.3+, 24.15+, or 25.9+ (installer defaults to Node 26). Install it from the official NodeSource repository:
curl -fsSL https://deb.nodesource.com/setup_26.x | sudo -E bash -
sudo apt-get install -y nodejs
node --version # Should show v26.x.x
Install openclaw.ai
Run the official one-line installer:
curl -fsSL https://openclaw.ai/install.sh | bash
Run Onboarding
Launch the interactive onboarding wizard. The --install-daemon flag automatically configures openclaw.ai to run as a background service:
openclaw onboard --install-daemon
The wizard will walk you through:
- Authentication setup (API keys for your LLM provider)
- Gateway configuration (port, allowed origins)
- Optional channel setup (Slack, Discord, etc.)
Verify Installation
Confirm everything is running correctly:
# Check system configuration
openclaw doctor
# Verify the gateway is healthy
openclaw health
# Print the authenticated dashboard URL
openclaw dashboard --no-open
# On your local computer, forward the private Gateway port
ssh -N -L 18789:127.0.0.1:18789 root@your-vps-ip
# Then open http://127.0.0.1:18789
Configure Hostinger Firewall
Keep the Gateway bound to loopback and expose only SSH. Access the dashboard through the tunnel from Step 7:
Via hPanel
- Go to VPS â Settings â Firewall
- Enable the firewall if not already active
- Add a rule allowing SSH (port 22) from your IP address
Via Command Line (ufw)
# Enable ufw and allow SSH first (important!)
sudo ufw allow 22/tcp
sudo ufw enable
sudo ufw status
Always Allow SSH First
Always add the SSH rule before enabling ufw, or you'll lock yourself out of the server. Do not open port 18789 publicly; the Gateway binds to loopback by default.
Keep Running with systemd
The --install-daemon flag from Step 6 already set up a systemd user service. To check its status:
# Check gateway status via openclaw CLI
openclaw gateway status
# Or check directly via systemd
systemctl --user status openclaw-gateway
# View live logs
journalctl --user -u openclaw-gateway -f
The service will automatically restart on failure and start on boot.
đ§ Troubleshooting
If you enabled ufw without allowing SSH first:
- Go to hPanel â VPS â Browser terminal
- Run:
sudo ufw allow 22/tcp - Verify with:
sudo ufw status
Check the Gateway on the VPS, then restart the tunnel on your local computer:
# On the VPS
openclaw gateway status
ss -tlnp | grep 18789
# On your local computer
ssh -N -L 18789:127.0.0.1:18789 root@your-vps-ip
Keep the SSH session open while using http://127.0.0.1:18789.
Check resource usage on the server:
# Check memory usage
free -h
# Check disk usage
df -h
# Check running processes
top
If OpenClaw shares the VPS with other services, resize the instance or remove unused workloads when memory remains constrained.
Ready to deploy? Get started with Hostinger â
Was this tutorial helpful?