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

Closed
Open
Created Jun 21, 2013 by Administrator@rootOwner

[stable-5.3] unable to clone when using a subdir (relative url root)

Created by: simkin

The following setting is used in both the gitlab.yml and puma.rb files:

 relative_url_root: /gitlab

When creating a new project the endpoint looks fine: image

The repository is created locally:

[git@appsysdev refs]$ pwd
/home/git/repositories/lmolenaar/tester.git/refs
[git@appsysdev refs]$ ls
heads  tags

When https cloning from my test server:

[lmolenaar@VM-TEST-SuSE:~] $git clone https://xxx.xxx.xxx/gitlab/lmolenaar/tester.git
Cloning into tester...
fatal: https://xxx.xxx.xxx/gitlab/lmolenaar/tester.git/info/refs not found: did you run git update-server-info on the server?

When ssh cloning:

[lmolenaar@VM-TEST-SuSE:~] $git clone [email protected]:lmolenaar/tester.git
Cloning into tester...
Tunnel device open failed.
Could not request tunnel forwarding.
warning: You appear to have cloned an empty repository.

No entries are added to any of the logfiles.

When I do NOT set the subdir in the configuration the http(s) cloning works fine. I make use of the Apache reverse proxy with a signed certificate

Assignee
Assign to
Time tracking