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

Closed
Open
Created Apr 08, 2013 by Administrator@rootOwner

nginx site adds IP address, breaks gitlab 5.0

Created by: sethvargo

On a fresh installation, following the newest guide, the nginx site template for gitlab has this:

server {
  listen YOUR_SERVER_IP:80 default_server;         # e.g., listen 192.168.1.1:80;
  # ...
}

If you actually put your server IP there, nginx will return 502s all day from any request made on your local machine if you have your hostname in the /etc/hosts file. That's because the request is going to 127.0.0.1, since it never leaves the local machine.

Since gitlab-shell uses the internal API, it fails. Removing the IP altogether and just listening on 80 (443 in my case actually) fixes the issue.

Assignee
Assign to
Time tracking