From 9920479665a36c00ee8c71d3a692147bb483008c Mon Sep 17 00:00:00 2001 From: Cal Corum Date: Thu, 19 Feb 2026 21:59:41 -0600 Subject: [PATCH] store: SSH known_hosts stale key when reusing LXC IP addresses --- ...stale-key-when-reusing-lxc-ip-addresses-321ce8.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 graph/fixes/ssh-known-hosts-stale-key-when-reusing-lxc-ip-addresses-321ce8.md diff --git a/graph/fixes/ssh-known-hosts-stale-key-when-reusing-lxc-ip-addresses-321ce8.md b/graph/fixes/ssh-known-hosts-stale-key-when-reusing-lxc-ip-addresses-321ce8.md new file mode 100644 index 00000000000..d509456d25b --- /dev/null +++ b/graph/fixes/ssh-known-hosts-stale-key-when-reusing-lxc-ip-addresses-321ce8.md @@ -0,0 +1,12 @@ +--- +id: 321ce884-ca3f-4c8d-945b-32069a857704 +type: fix +title: "SSH known_hosts stale key when reusing LXC IP addresses" +tags: [proxmox, ssh, homelab, fix] +importance: 0.6 +confidence: 0.8 +created: "2026-02-20T03:59:41.688515+00:00" +updated: "2026-02-20T03:59:41.688515+00:00" +--- + +When provisioning CT 302 (claude-runner) at 10.10.0.148 (same IP as deleted LXC 300), SSH connections failed with "REMOTE HOST IDENTIFICATION HAS CHANGED" on both desktop and N8N LXC. Fix: `ssh-keygen -R 10.10.0.148` on each client that previously connected to the old LXC, then reconnect with `-o StrictHostKeyChecking=accept-new`. Had to clear it on desktop (known_hosts:27) and on N8N LXC (known_hosts:1).