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

Closed
Open
Created Dec 06, 2011 by Administrator@rootOwner

Gitolite support not using custom port?

Created by: cubehouse

Hi, Just checked out the master branch on Ubuntu and installed Gitlab using the provided scripts. I configured Gitlab to use a different port like so:

  system: gitolite
  admin_uri: [email protected]:gitolite-admin
  base_path: /home/git/repositories/
  host: git.mydomain.com
  git_user: git
  port: 2000

However, I get errors when trying to add projects etc. in Gitlab. I checked the logs and I see this:

fatal: The remote end hung up unexpectedly

Looks to me like the port isn't being used when connecting to Gitolite?

Assignee
Assign to
Time tracking