sameersbn / sameersbn/docker-gitlab
Git push/pull not working remotely, but works fine within local network
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
I have a Synology Diskstation 415+ running Docker 1.11 and Gitlab 8.6.2-0018. My SSH port is on default port 22, I kept the gitlab container ports on 30000 and 30001. I have both ports redirected properly and Gitlab's web interface comes up fine remotely. From within the local network, we are able to git pull/push to gitlab repos without any problem. However, if we try to git push/pull/clone from a remote computer (which also has its SSH keys added to the user profile) we get this message:
ssh: connect to host ourdevserver.com port 30001: Connection timed out
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
Start by reviewing the Synology DiskStation Docker port mappings and the SSH configuration described in the issue, focusing on ports 22, 30000, and 30001. Compare connectivity from the local and remote networks and verify the GitLab remote endpoint; done means remote users can clone, pull, and push successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, git, shell
- Domain
- devops, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100