Nexus 3.0 Hard Boot Recovery Protocol

Last Updated: January 13, 2026
Status: CRITICAL - Use after server hard reboot

KEY DISCOVERY: Docker Container Restart Fix

THE FIX: After hard reboot, Docker containers may have Redis running internally but ports not exposed to host.

SOLUTION: Restart the Docker containers:

docker restart nexus3-{env}-vault nexus3-{env}-operational

This makes the ports listen on the host system where MCP servers can reach them.

Critical Environments for Handoff

Must be working for proper handoff:

1. KB (6625/6626) - Password: KB3Vault2025
2. Restart: docker restart nexus3-kb-vault nexus3-kb-operational

3. Test: redis-cli -p 6625 -a "KB3Vault2025" PING

4. Workflow (6615/6616) - Password: Workflow3Vault2025

5. Restart: docker restart nexus3-workflow-vault nexus3-workflow-operational

6. Test: redis-cli -p 6615 -a "Workflow3Vault2025" PING

7. Session (6645/6646) - Password: Session3Vault2025

8. Restart: docker restart nexus3-session-vault nexus3-session-operational

9. Test: redis-cli -p 6645 -a "Session3Vault2025" PING

10. Chrono (6680/6681) - Password: Temp3Vault2025

11. Restart: docker restart nexus3-chrono-vault nexus3-chrono-operational

12. Test: redis-cli -p 6680 -a "Temp3Vault2025" PING

13. aimsg (6690/6691) - Password: 6PYyEw

14. Usually works without restart (standalone Redis)
15. Test: redis-cli -p 6690 -a "6PYyEw" PING

Password Mismatch Issue

Problem: MCP servers expected old strong passwords from Locker (e.g., tg6ap5) but Docker containers use new weak passwords (e.g., KB3Vault2025).

Quick Fix: Update MCP server fallback passwords to match Docker:

1. KB: /opt/mcp-servers/kb/mcp_kb_server.py line ~78

2. Change: vault_password = 'tg6ap5' → vault_password = 'KB3Vault2025'

3. Workflow: /opt/mcp-servers/workflow/mcp_workflow_server.py line ~84

4. Change: REDIS_PASSWORD = 'VFLtfX' → REDIS_PASSWORD = 'Workflow3Vault2025'

5. Repeat for other environments as needed

Recovery Checklist

After hard reboot:

• [ ] Check Docker containers running: docker ps | grep nexus3-
• [ ] Verify data exists: docker exec nexus3-kb-vault redis-cli -a "KB3Vault2025" DBSIZE
• [ ] Restart KB containers
• [ ] Restart Workflow containers
• [ ] Restart Session containers
• [ ] Restart Chrono containers
• [ ] Test KB: redis-cli -p 6625 -a "KB3Vault2025" PING
• [ ] Test Workflow: redis-cli -p 6615 -a "Workflow3Vault2025" PING
• [ ] Test Session: redis-cli -p 6645 -a "Session3Vault2025" PING
• [ ] Test Chrono: redis-cli -p 6680 -a "Temp3Vault2025" PING
• [ ] Test aimsg: redis-cli -p 6690 -a "6PYyEw" PING

Success Criteria

System ready for handoff when: - ✅ KB accessible (search working) - ✅ Workflow accessible (init working) - ✅ Session accessible (objectives retrievable) - ✅ Chrono accessible (date/time available) - ✅ aimsg accessible (handoff system operational)

First Recovery: January 12-13, 2026 - 100% success, zero data loss