sameersbn / sameersbn/docker-gitlab

error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500

Open
#2,418 6 comments 0 reactions 0 assignees View on GitHub

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 am using Sameersbn/gitlab 14.1.1, we are seeing the error "error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500" very frequently when developers are trying to fetch the repos from IDEs(Intellij) or local CMDs.

Here is my configuration

System information
System:
Current User: git
Using RVM: no
Ruby Version: 2.7.2p137
Gem Version: 3.1.4
Bundler Version:2.1.4
Rake Version: 13.0.3
Redis Version: 5.0.7
Git Version: 2.32.0
Sidekiq Version:5.2.9
Go Version: unknown

GitLab information
Version: 14.1.1
Revision: c8edb9de30c
Directory: /home/git/gitlab
DB Adapter: PostgreSQL
DB Version: 12.3
URL: http://xxxxxxxxxx
HTTP Clone URL: http://xxxxxxxxxx
SSH Clone URL: ssh://git@xxxxxxxxxxxxxxx
Using LDAP: yes
Using Omniauth: no

GitLab Shell
Version: 13.19.0
Repository storage paths:

  • default: /home/git/data/repositories
    GitLab Shell path: /home/git/gitlab-shell
    Git: /usr/bin/git

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 HTTP Clone URL and GitLab Shell 13.19.0 entry points, using the reported Git 2.32.0, PostgreSQL 12.3, and GitLab 14.1.1 versions. Reproduce a fetch from an IDE or local command line and inspect the server-side failure behind the HTTP 500. Done means the cause is identified and repository fetches complete reliably.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, git, postgresql, redis, ruby
Domain
backend, devops
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.