Ona GCP Runner Not Connected: Terraform, Health Check and Zone Resource Errors

Q: How do I fix "Ona GCP Runner Not Connected: Terraform, Health Check and Zone Resource Errors"?

1. Fix permissions and network: Compare service account roles with the Access Requirements page Add Cloud NAT or external IPs; enable Private Google Access Allow port 29222 and outbound HTTPS Run curl -v https://your-domain.com/_health and expect 200 2. Capacity errors: Add more zones in terraform.tfvars Change runner_vm_config.machine_type, for example e2-standard-4 Retry later, then restart instances after network changes

Workaround available GCP Updated November 14, 2026How we research

Quick answer

GCP runner failures come from missing Cloud NAT, firewall rules, IAM roles or zone capacity. Check the /_health endpoint and confirm the runner shows Connected in Settings > Runners.

Most likely fix: Fix permissions and network

How to fix it

Try these in order — the most common fix is first.

1. Fix permissions and network
1. Compare service account roles with the Access Requirements page
2. Add Cloud NAT or external IPs; enable Private Google Access
3. Allow port 29222 and outbound HTTPS
4. Run curl -v https://your-domain.com/_health and expect 200
Did this fix it?
2. Capacity errors
1. Add more zones in terraform.tfvars
2. Change runner_vm_config.machine_type, for example e2-standard-4
3. Retry later, then restart instances after network changes
Did this fix it?