Geek Answers Handbook

Cloning error of gitlab project with https

I have a problem when I try to clone my Gitlab project with the "https" protocol. With git protocol, everything works fine.

Mistake:

Cloning into 'test'... fatal: https://XXXX.XXXX.XXXX.XXXX/user.name/test.git/info/refs?service=git-upload-pack not found: did you run git update-server-info on the server?

I tried many solutions, but the error is still here.

Can anybody help me?

Thanks for the help and have a nice day!

+7
source share
3 answers

My problem was in the Apache configuration file. My configuration example

 <VirtualHost ip:80> ServerName git.domain.tld Redirect permanent / https://git.domain.tld/ </VirtualHost> <VirtualHost ip:443> ServerName git.domain.tld DocumentRoot /home/git/gitlab/public <Location /> ProxyPassReverse http://127.0.0.1:8080 ProxyPassReverse http://git.domain.tld </Location> RewriteEngine on RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f RewriteRule .* http://127.0.0.1:8080%{REQUEST_URI} [P,QSA] RequestHeader set X_FORWARDED_PROTO 'https' </VirtualHost>

Source: https://github.com/gitlabhq/gitlab-recipes/tree/master/web-server/apache

+2
source

A common source of this error is some error in the URL. Make sure everything is in order. Can you clone via HTTP? Is your server installed to serve the repository over HTTP and HTTPS?

If your client is git (read the output of git --version ), it will not be able to use the endpoint of smart HTTP.

Commentary in Problem GitLab # 1924 suggests resolving server-side permission problems.

0
source

This error can occur if you change the default configuration for the relative_url_root variable for the gitlab application in the configuration file .../gitlab/config/gitlab.yml . The default value is / . When you change the default value like /gitlab , url will be

  http://your.domain/gitlab

This is shown as the cloning URL for the project in the user interface is correct, for example

  http://your.domain/gitlab/group/project.git

but somehow this configuration is not checked when performing the actual cloning via http or https.

There has already been a discussion and fix on gitub on this in the gitlab list of issues. Here is the source file .

My configuration is gitlab v5.0 and gitlab-shell v1.1.0.

0
source

More articles:


All Articles