store: N8N runner key (ed25519) for CT 302 automation access
This commit is contained in:
parent
9920479665
commit
270db022f2
@ -0,0 +1,12 @@
|
|||||||
|
---
|
||||||
|
id: d00e90ce-51ab-4a01-bf28-62e5020a354c
|
||||||
|
type: configuration
|
||||||
|
title: "N8N runner key (ed25519) for CT 302 automation access"
|
||||||
|
tags: [n8n, ssh, monitoring, homelab]
|
||||||
|
importance: 0.7
|
||||||
|
confidence: 0.8
|
||||||
|
created: "2026-02-20T03:59:47.354482+00:00"
|
||||||
|
updated: "2026-02-20T03:59:47.354482+00:00"
|
||||||
|
---
|
||||||
|
|
||||||
|
Generated dedicated ed25519 key on N8N LXC (10.10.0.210) for SSH access to CT 302. Key pair at `/root/.ssh/n8n_runner_key` on N8N LXC. Public key added to CT 302's `/root/.ssh/authorized_keys`. Tested full pipeline: N8N → SSH with n8n_runner_key → CT 302 → health_check.py → SSH with homelab_rsa → target servers → JSON output with exit code. Command from N8N: `ssh -i /root/.ssh/n8n_runner_key root@10.10.0.148 'cd /root/.claude/skills/server-diagnostics && .venv/bin/python3 health_check.py --dry-run'`
|
||||||
Loading…
Reference in New Issue
Block a user