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

Closed
Open
Created May 23, 2014 by Administrator@rootOwner

Different external_url and port not working

Created by: thextra

When using chef coming with the latest GitLab package (gitlab_6.9.0-omnibus-1_amd64.deb) changing of listening port and external_url came into conflict.

I've tried, after successful installation, to change the port GitLab is listening on to something else then port 80 and change the external_url to a subdomain with port 80 (requests will be handled by a proxy).

My /etc/gitlab/gitlab.rb looks like that:

external_url "http://git.example.com"
gitlab_rails['gitlab_port'] = 8001

But GitLab will continue listening on port 80 anyway.

If you only use external_url like external_url "http://git.example.com:8001" GitLab will listen on port 8001 but also will add :8001 to all URLs (which is not desired).

Assignee
Assign to
Time tracking