When creating a claw for a github issue factory, the claw never bootstrapped but had this error:
# journalctl -fu elasticclaw
May 21 22:20:12 replicated-factory elasticclaw[184407]: 2026/05/21 22:20:12 Replicated VM 4288bb9c terminated
May 21 22:20:14 replicated-factory elasticclaw[184407]: 2026/05/21 22:20:14 [poll] tick: 4 factories loaded, evaluating integrations
May 21 22:20:29 replicated-factory elasticclaw[184407]: 2026/05/21 22:20:29 Warning: failed to write template files: ssh dial: dial tcp 135.181.62.232:36361: connect: connection refused
May 21 22:20:29 replicated-factory elasticclaw[184407]: 2026/05/21 22:20:29 SSH attempting: user=elasticclaw host=135.181.62.232:36361 key-type=ssh-ed25519 fingerprint=SHA256:bSOwlgMUqZrMqYF9HCCIHuRaICFyRR6Q3hy6Fp/pGeM
May 21 22:20:29 replicated-factory elasticclaw[184407]: 2026/05/21 22:20:29 SSH public key being used:
May 21 22:20:29 replicated-factory elasticclaw[184407]: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIM+TEUY0Zhlksa99wA4qFGGnxcXrayHpEszSF2OanLNn elasticclaw@hub
May 21 22:20:29 replicated-factory elasticclaw[184407]: 2026/05/21 22:20:29 [bootstrap] warning: cred helper setup failed: ssh dial 135.181.62.232:36361: dial tcp 135.181.62.232:36361: connect: connection refused
May 21 22:20:29 replicated-factory elasticclaw[184407]: 2026/05/21 22:20:29 Bootstrap complete for claw schemahero/schemahero/1366 (60b96aec)
that makes sense, but IMO we should be more resilient
When creating a claw for a github issue factory, the claw never bootstrapped but had this error:
that makes sense, but IMO we should be more resilient