Geek asks and answers

GitLab: Can't get the code to the server?

I installed GitLab on an Ubuntu server. Everything seems to be working fine, except that I cannot push / pull / clone to / from the server.

When I click, I get a general error message:

fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

I tried everything from hours on the Internet, but I can not find the problem.

sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production

It works fine, OK in all directions!

I can use SSH in git @ adress.adress I get:

PTY allocation request failed on channel 0
Welcome to GitLab, Anonymous!

When I do this:

ssh git@adress.adress "ls /location/of/git/dir"

I get:

Not allowed command

The website works when I create a repository on the site that it appears in / home / git / repository /

But I still can’t click on it.

I followed this guide:

https://github.com/gitlabhq/gitlabhq/blob/5-0-stable/doc/install/installation.md

and this guide to run it on apache:

http://shanetully.com/2012/08/running-gitlab-from-a-subdirectory-on-apache/

+5
6

, , , - , .

, gitlab apache URL, gitlab. URL: s unicorn.rb gitlab-shell/config URL ( ).

:

 http://web-adress.com/


 http://web-adress.com/subdomain/

.

+7

. .

ssh -T git @myserver.com

GitLab, !

" GitLab, !" gitlab gitlab.

+4

, , , , gitlab, . , :

ssh-keygen -t rsa -C "#email address#"

ssh-, .

/ RSA.

, SSH GitLab

cat ~/.ssh/#key name#.pub

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC6eNtGpNGwstc....*
+1

( " 6 17:23" " 21 10:07" "Joakim Engstrom" ):

, , Gitlab, ( http://localhost/<my_context_path>, http://localhost).

gitlab-shell:

// logout any Gitlab open session, stop your Gitlab service, and your possible third-party webserver first  
$ sudo service apache2 stop  
$ sudo service gitlab stop  

// perform the modification that fixes it, if you indeed configured Gitlab to be accessed with a custom context path  
$ sudo -u git -H nano ~git/gitlab-shell/config.yml  

# Url to gitlab instance. Used for api calls. Should end with a slash.
-gitlab_url: "http://localhost/"
+gitlab_url: "http://localhost/<my_context_path>/"

// restart services  
$ sudo service gitlab start  
$ sudo service apache2 start  

// Try to push again from your particular Gitlab user local repository, to the Gitlab remote repository    
$ cd <path_to_my_local_repository>  
$ sudo -u <OS_username_that_owns_the_local_repository> -H git push -u origin master  
Counting objects: 3202, done.  
Delta compression using up to 2 threads.  
Compressing objects: 100% (3115/3115), done.  
Writing objects: 100% (3202/3202), 11.56 MiB | 5.34 MiB/s, done.  
Total 3202 (delta 609), reused 0 (delta 0)  
To `git@<my_FQDN>:<my_Gitlab_user_or_group_name>/<my_gitlab_project_ID>.git`  
  * [new branch]      master -> master  
Branch master set up to track remote branch master from origin.  
$

" stackoverflow.com/questions/13071234/... - Paul Verest 18 6:20" ( gitlab):
, .

+1

https nginx. , git gitlab-api,

sudo -u git -H /home/git/gitlab-shell/bin/check

.

Check GitLab API access: FAILED. code: 301

gitlab_url /home/git/gitlab-shell/config.yml https://<domain>

0

, , ssh /etc/ssh/sshd _config AllowUsers git

0

More articles:


All Articles