🔐
Restricted Access
This section is for authorized personnel only.
Enter the access password to continue.
Contact the operations team if you need access.
✅ Access granted. These are general recovery steps. Sensitive credentials are stored separately in the operations document — do not store them here.
⚠️ Handle with care. These procedures affect live systems. When in doubt, do nothing and contact the operations lead directly.
Scenario A — JarBibi Not Responding
1
SSH into the VPS using the credentials from your secure operations document.
2
Check if the Docker container is running:
docker ps -a | grep openclaw
If status shows Exited or Restarting — the container has crashed.
3
Attempt a simple restart first:
docker restart $(docker ps -aq --filter name=openclaw)
Wait 30 seconds, then run docker ps. If status is Up — JarBibi is back online. ✓
Scenario B — Container Won't Start
1
Check the container logs for the error:
docker logs --tail 50 $(docker ps -aq --filter name=openclaw)
2
If the config appears corrupted, restore from a backup. Backup files exist at numbered .bak paths alongside the main config. Choose the most recent clean backup and copy it over.
3
Recreate the container:
docker stop $(docker ps -aq --filter name=openclaw)
docker rm $(docker ps -aq --filter name=openclaw)
cd /home/jarbibi && docker compose up -d
Scenario C — Need Claude's Help
1
Go to claude.ai and open the JarBibi Project.
2
Paste the full JARBIBI_CORE_DETAILS file (stored in your secure notes) and explain what's happening. Claude will guide you through the fix step by step.
⚠️ Critical Rules — Never Break These
NEVER delete /home/jarbibi/.openclaw/ — this is all of JarBibi's config, memory, and data. It survives container rebuilds because it's a mounted volume. Deleting it means starting from scratch.
NEVER set gateway.auth.mode to "open" — this is not a valid mode and caused a 24-hour crash loop previously. Valid modes only: token, password, pairing.
NEVER kill the gateway process from inside the container — always use docker restart from the VPS host.
NEVER patch or edit files inside the container at runtime — changes are wiped on restart. Only the mounted .openclaw volume persists.