Ambiguous key verification error
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github-actions, typescript
Research direction
Start by reproducing the failure with php vendor/bin/dep deploy test -v --no-interaction --ansi -vvv and inspect the SSH multiplexing initialization output shown in the issue. Done means the host key verification error identifies which host or key caused the failure, including during the deploy failure and unlock steps.
Written by the indexing model from the issue text.
Description
With the recent change to githubs RSA fingerprints we had to update the SSH known hosts secret, but unfortunately github was not the only thing in there ( is there ever a situation were this deployer would run and not need to know the github SSH? ).
However github was not the only host listed, and now deployment fails with host key verification failed, but which key? Who is the host? My key? The private key in secrets? The server we're deploying to? How do I find out?
Here's the output, I've swapped out the IP for 1.2.3.4:
$ php vendor/bin/dep deploy test -v --no-interaction --ansi -vvv
✈︎ Deploying deploy-test on 1.2.3.4
• done on [1.2.3.4]
➤ Executing task deploy:prepare
[23.94.156.6] > echo $0
[23.94.156.6] < ssh multiplexing initialization
[23.94.156.6] < Host key verification failed.
➤ Executing task deploy:failed
• done on [1.2.3.4]
✔ Ok [0ms]
➤ Executing task deploy:unlock
[23.94.156.6] > rm -f ~/deploy/.dep/deploy.lock
[23.94.156.6] < ssh multiplexing initialization
[23.94.156.6] < Host key verification failed.
Also noting that this is an inherited setup, the person who originally set this up is long gone and unavailable
Upvote & Fund
- We're using Polar.sh so you can upvote and help fund this issue.
- We receive the funding once the issue is completed & confirmed by you.
- Thank you in advance for helping prioritize & fund our backlog.
- Dominant language
- TypeScript
- Stars
- 269
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from deployphp/action
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
-
Puzzling ssh fail Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in deployphp/action
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
dennys-bd/agent-hive#184 ·
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vicharanashala/fln#563 ·