From 845b578606c0c5a956c70caf61e00a7d2b13ee37 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dragan=20Filipovi=C4=87?= Date: Wed, 31 Jan 2024 01:59:36 +0100 Subject: [PATCH] fix: Add info for Permission denied issue. --- README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/README.md b/README.md index a56b094..d84fbe0 100644 --- a/README.md +++ b/README.md @@ -146,6 +146,9 @@ These issues are not related to the action itself. - Check manually your ssh connection from your client before opening a bug report. - Check `rsync` params for your use-case. Default params are not necessarily going to be enough for everyone, it highly depends on your setup. - Check manually your rsync command from your client before opening a bug report. +- `Deployment Failed, Permission denied (publickey,password)`: This issue occures in some cases, it is related to OS and ssh. This action can only provide a workaround: + - Use `SCRIPT_BEFORE` param, eg `SCRIPT_BEFORE: ls`. This will force `known_hosts` update, adding your host via `ssh-keyscan`. + - Or manually add public key to authorized_keys and add a new line to a private key. I've added e2e test for this action. Real example is executed on every PR merge to `main`.