sameersbn / sameersbn/docker-gitlab
Rancher 2.x Can't connect to repository with ssh
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hi,
I tried to find the way out of this issue but no luck.
Pods:
- Forward port 30022/tcp to 22/tcp
- Already set GITLAB_SSH_PORT = 30022
I already run this script in VPS that run GitLab pod. But I got this message when trying to clone repository via ssh:
ssh: connect to host gitlab.my_domain.com port 30022: Connection refused
It's fine when I changed to https connection. Hope somebody could give me the experience with Rancher 2.x!
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
Start with the reported Rancher 2.x port mapping, GITLAB_SSH_PORT=30022, and contrib/expose-gitlab-ssh-port.sh. Reproduce the SSH clone failure and inspect how the forwarded port reaches the GitLab container, using the HTTPS path as a comparison. Done means SSH connections to gitlab.my_domain.com:30022 succeed; the issue does not identify a project file or test to change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, git, gitlab, shell
- Domain
- devops, infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100