sameersbn / sameersbn/docker-gitlab

SSH Operation timed out

Open
#1,522 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

wontfix
Dominant language
Shell
Stars
8.1k
Forks
2.1k
Avg merge
17h 47m
Merged PRs (30d)
7

Description

I'm trying to push a rather big repo that has a bunch of images, and I got this output when pushing to the repo:

❯ git push -u origin master
warning: redirecting to https://git.website.com/perryprog/repo
Counting objects: 285, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (283/283), done.
Writing objects: 100% (285/285), 109.48 MiB | 9.56 MiB/s, done.
Total 285 (delta 3), reused 0 (delta 0)
error: RPC failed; HTTP 413 curl 22 The requested URL returned error: 413 Request Entity Too Large
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date

A quick search said to use SSH, and it seems my SSH isn't set up properly either.

ssh: connect to host git.website.com port 10022: Operation timed out
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Relevant config options:

    ports:
    - "80:80"
    - "433:433"
    - "10022:10022"
    - "587:587"
    - "993:993"
# ...
    - GITLAB_SSH_PORT=10022

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the relevant YAML configuration, focusing on the 10022 port mapping and GITLAB_SSH_PORT. Reproduce the SSH connection and large push, then verify that the configured SSH endpoint is reachable and the reported push errors no longer occur.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, git, 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.