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
  • #3882

Closed
Open
Created May 08, 2013 by Administrator@rootOwner

Pushing big commits over HTTPS gives a 502

Created by: foux

Hello, I'm using github 5.1 with Apache. Pushing via ssh works like a charm, but when I try to push large commits via https, I've got this problem 👍

Counting objects: 45514, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (11158/11158), done.
Writing objects: 100% (45514/45514), 21.16 MiB | 135 KiB/s, done.
Total 45514 (delta 33925), reused 45323 (delta 33776)
error: RPC failed; result=22, HTTP code = 502
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date

My apache error logs prints this : (103)Software caused connection abort: proxy: pass request body failed to 127.0.0.1:3000 (127.0.0.1) proxy: pass request body failed to 127.0.0.1:3000 (127.0.0.1) from 2.12.157.247 ()

I've got nothing in my application log, nor in the puma logs.

Any idea on how to solve this? Thanks

Assignee
Assign to
Time tracking