sameersbn / sameersbn/docker-gitlab
Host key verification failed when cloning from ssh
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hello,
I'm having problems when I try to clone repository via SSH. Over http it works fine.
I've added my public key to my account.
What might be the problem?
Does it mean that my local git client is refusing to read from the remote or the other way around, that it is the gitlab that refuses to comply?
$ git clone ssh://git@gitlab.local:2222/tarach/test.git
Cloning into 'test'...
Host key verification failed.
fatal: Could not read from remote repository.Please make sure you have the correct access rights
and the repository exists.
Contributor guide
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.
Research direction
No source file, test, or entry point is named in the issue. Start by reproducing the shown SSH clone command and tracing the local client and GitLab container configuration involved in host-key verification. Done means clearly identifying the failing side and documenting a verified resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, git
- Domain
- devops, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100