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

Closed
Open
Created Dec 09, 2012 by Administrator@rootOwner

Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.

Created by: temenb

I installed gitlab following to the manual ( https://github.com/gitlabhq/gitlabhq/blob/stable/doc/install/installation.md ) Then I went to the file "config/unicorn.rb" and added the line "listen 8081" (And also I changed port in the the gitlab.yml.. if it does matter)

when I try go by url http://localhost:8081 I'm redirected to http://localhost:8081/users/sign_in where I see Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data.

I tried to install gitlab on the virtual machine, and I had the same result. But after few page reloading error have gone and gitlab started work well! Unfortunately this trick doesn't work with the server machine.

UPD: I was managed to start gitlab via apache2+passenger. But via unicorn trouble is still present.

Assignee
Assign to
Time tracking