Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #5016

Closed
Open
Created Sep 09, 2013 by Administrator@rootOwner

[Bug]'git clone' http access 502 ,ssh is working well

Created by: blackjack550

hello, my repo cant git clone by http link,but ssh is working well.my repo size is 954M. i got error:

git.exe clone --progress -v "http://gitlab-pro/blackjack/autofiles.git" "V:\git\autofiles"

Cloning into 'V:\git\autofiles'... POST git-upload-pack (250 bytes) fatal: The remote end hung up unexpectedly error: RPC failed; result=22, HTTP code = 502

git did not exit cleanly (exit code 128) (39500 ms @ 2013/9/9 9:59:49)

then,i test another project in the server.i can git clone by http.the project is different size with another project. please help me. thx!

my nginx config: http { client_max_body_size 10000m; include mime.types; default_type application/octet-stream;

#log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
#                  '$status $body_bytes_sent "$http_referer" '
#                  '"$http_user_agent" "$http_x_forwarded_for"';

#access_log  logs/access.log  main;

sendfile        on;
#tcp_nopush     on;

#keepalive_timeout  0;
keepalive_timeout  65;

#gzip  on;

upstream gitlab { server unix:/opt/git/gitlab/tmp/sockets/gitlab.socket; }

server { listen 80; # e.g., listen 192.168.1.1:80; root /opt/git/gitlab; chunkin on;

individual nginx logs for this gitlab vhost

access_log logs/gitlab_access.log; error_log logs/gitlab_error.log;

location / { # serve static files from defined root folder;. # @gitlab is a named location for the upstream fallback, see below try_files $uri $uri/index.html $uri.html @gitlab; }

if a file, which is not found in the root folder is requested,

then the proxy pass the request to the upsteam (gitlab unicorn)

location @gitlab { proxy_read_timeout 300; # https://github.com/gitlabhq/gitlabhq/issues/694 proxy_connect_timeout 300; # https://github.com/gitlabhq/gitlabhq/issues/694 proxy_redirect off;

proxy_set_header   X-Forwarded-Proto $scheme;
proxy_set_header   Host              $http_host;
proxy_set_header   X-Real-IP         $remote_addr;

proxy_pass http://gitlab;

} } my gitlab config: #3 (closed). Advanced settings

==========================

GitLab Satellites

satellites: # Relative paths are relative to Rails.root (default: tmp/repo_satellites/) path: /opt/git/gitlab-satellites/

Backup settings

backup: path: "tmp/backups" # Relative paths are relative to Rails.root (default: tmp/backups/) # keep_time: 604800 # default: 0 (forever) (in seconds)

GitLab Shell settings

gitlab_shell: # REPOS_PATH MUST NOT BE A SYMLINK!!! repos_path: /opt/git/repositories/ hooks_path: /opt/git/gitlab-shell/hooks/

# Git over HTTP
upload_pack: true
receive_pack: true

# If you use non-standard ssh port you need to specify it
# ssh_port: 22

Git settings

CAUTION!

Use the default values unless you really know what you are doing

git: bin_path: /usr/bin/git # Max size of a git object (e.g. a commit), in bytes # This value can be increased if you have very large commits max_size: 5242880000 # 5.megabytes # Git timeout to read a commit, in seconds timeout: 10

Assignee
Assign to
Time tracking