From 6acfc3f121df6c5ca732186c3a6617b80b2322b9 Mon Sep 17 00:00:00 2001 From: rcourtman Date: Sun, 19 Oct 2025 08:39:55 +0000 Subject: [PATCH] fix: use id_rsa in SSH config instead of id_ed25519 The setup script was generating SSH config with IdentityFile ~/.ssh/id_ed25519 but Pulse generates id_rsa keys. Updated SSH config template to use id_rsa to match the actual key type generated by the monitoring system. --- internal/api/config_handlers.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/internal/api/config_handlers.go b/internal/api/config_handlers.go index 7c3bc0e..8207eb1 100644 --- a/internal/api/config_handlers.go +++ b/internal/api/config_handlers.go @@ -3947,7 +3947,7 @@ elif [ "$TEMP_MONITORING_AVAILABLE" = true ]; then SSH_CONFIG="Host ${PROXY_JUMP_HOST} HostName ${PROXY_JUMP_IP} User root - IdentityFile ~/.ssh/id_ed25519 + IdentityFile ~/.ssh/id_rsa StrictHostKeyChecking accept-new " @@ -3958,7 +3958,7 @@ elif [ "$TEMP_MONITORING_AVAILABLE" = true ]; then Host ${NODE} ProxyJump ${PROXY_JUMP_HOST} User root - IdentityFile ~/.ssh/id_ed25519 + IdentityFile ~/.ssh/id_rsa StrictHostKeyChecking accept-new " fi