#ACP runtime "unavailable" on v2026.3.23 β€” all known workarounds tried, still blocked

1 messages Β· Page 1 of 1 (latest)

bold shuttle
#

Hey everyone, hoping someone can help. I've spent most of today trying to get the ACP runtime working and I'm completely stuck. Here's everything:

Environment:

OpenClaw: 2026.3.23
OS: Ubuntu 22.04 LTS (x86_64)
Node: v22.22.1
NPM: 10.9.4
VPS Host: Hostinger
Error:
Every sessions_spawn with runtime: "acp" fails with:
ACP runtime backend is currently unavailable. Try again in a moment.

Everything I've tried:

Enabled ACP Enabled toggle and set ACP Backend to acpx in the settings UI
Installed acpx plugin via clawhub install acpx --force
Set plugins.entries.acpx.config.expectedVersion = "any" (workaround from issue #43997)
Set plugins.entries.acpx.enabled = true in config
Multiple gateway restarts
Full VPS reboot
Verified PATH and Node.js are correctly set up
Related Issues Found:

#30807 β€” describes the same "backend unavailable" symptom
#43997 β€” version mismatch bug with the expectedVersion: "any" workaround (which I applied but didn't solve it)
Additional finding:
Running openclaw --version directly in the VPS terminal returns command not found, even though the gateway is running and the web UI is accessible. This suggests the CLI tools were not installed correctly system-wide on the Hostinger VPS, which may be the actual root cause preventing the acpx subprocess from launching.

I'm about to do a full VPS wipe and fresh reinstall on Hostinger. Before I do, is there anything I'm missing? Is there a recommended install method that ensures the openclaw CLI is correctly available system-wide after install on a Hostinger VPS or similar cloud provider?

Any help appreciated. Thanks.