From f358b68663fc2dd0198462d43fe56000301dc3f9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabian=20Gr=C3=BCnbichler?= Date: Thu, 21 Dec 2023 10:29:21 +0100 Subject: [PATCH] fix #5140: qdevice SSH access documentation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit rephrase in order to not make it seem like password-based access is required. Signed-off-by: Fabian Grünbichler --- pvecm.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/pvecm.adoc b/pvecm.adoc index 48d86bc..e381eb5 100644 --- a/pvecm.adoc +++ b/pvecm.adoc @@ -1056,13 +1056,13 @@ pve# pvecm qdevice setup The SSH key from the cluster will be automatically copied to the QDevice. -NOTE: Make sure that the SSH configuration on your external server allows root -login via password, if you are asked for a password during this step. +NOTE: Make sure to setup key-based access for the root user on your external +server, or temporarily allow root login with password during the setup phase. If you receive an error such as 'Host key verification failed.' at this stage, running `pvecm updatecerts` could fix the issue. -After you enter the password and all the steps have successfully completed, you -will see "Done". You can verify that the QDevice has been set up with: +After all the steps have successfully completed, you will see "Done". You can +verify that the QDevice has been set up with: ---- pve# pvecm status