WarningNetwork
Can't access OpenClaw on port 3000
OpenClaw is running but you can't reach it in your browser. This is almost always a firewall or networking issue — the container is fine, but traffic can't get through.
Symptoms
- •
Browser shows 'This site can't be reached' or times out - •
curl: (7) Failed to connect to server port 3000 - •
Works on the server locally but not from your computer
Causes
- •Cloud firewall is blocking port 3000 (Hostinger, Hetzner, AWS, etc.)
- •Container is not actually running
- •Binding to 127.0.0.1 instead of 0.0.0.0
- •Using the wrong IP address
Solution
Step 1: Verify the container is running
docker compose psYou should see the openclaw container with status "Up". If not, start it:
docker compose up -dStep 2: Test locally on the server
curl http://localhost:3000If this works, the container is fine — the problem is network/firewall.
Step 3: Open the port in your cloud firewall
Hostinger: VPS dashboard > Firewall > Add Rule > Port 3000, TCP, Allow
Hetzner: Cloud Console > Firewalls > Add Rule > Port 3000 TCP Inbound
AWS: Security Groups > Inbound Rules > Custom TCP, Port 3000, 0.0.0.0/0
DigitalOcean: Networking > Firewalls > Inbound Rules > TCP 3000
Step 4: Check the port mapping
Make sure your docker-compose.yml maps to all interfaces:
ports:
- "3000:3000" # Correct — binds to 0.0.0.0
# NOT "127.0.0.1:3000:3000" — this only allows localhostStep 5: Access with the correct IP
Use your server's public IP, not localhost:
http://YOUR_SERVER_IP:3000