Error 302 on check
Closed
Error 302 on check
Created by: djgreg13
Hello
When i do a sudo -u git -H /home/git/gitlab-shell/bin/check
i get this
Check GitLab API access: FAILED. code: 302
Check directories and files: /home/git/repositories: OK /home/git/.ssh/authorized_keys: OK
i have missed someone when i migrated to 5.0 from 4.2 ?
Created by: djgreg13
I can but gitlab is in under NAT and the domain don't respond same in network
in internal network it can be accessed by http://gitlab.interne.domain.com in external the acceess is http://git.domail.com
By Administrator on 2013-04-02T15:43:25 (imported from GitLab project)
Created by: djgreg13
Resolved, for other users
if you're into a NAT network, add your public domain into hosts file and point this at your localhosy same this 127.0.0.1 git.domain.com
and put the public adress in gitlab-shell config.yml
thanks allc ;)
By Administrator on 2013-04-02T15:49:07 (imported from GitLab project)
Created by: flakrat
I ran into this on a new install. The issue, I have the rewrite rule to force SSL (port 443) and am using a self signed cert.
I needed to modify gitlab-shel/config.yml as follows, change http to https and self_signed_cert from false to true:
gitlab_url: "https://gitlab.mydomain.org/" http_settings: self_signed_cert: true
By Administrator on 2013-08-29T17:18:58 (imported from GitLab project)
Created by: qfox
Actually there was a double slash in url. It can be a reason to force 302 error code if the web server configured to remove double slashes. Probably not, but. Anyway, it could be better if url will be clean.
host method in gitlab-shell/lib/gitlab_net.rb is defined as "#{config.gitlab_url}/api/v3/internal", and at the same time config.gitlab_url defined in ./gitlab-shell/config.yml "Should end with a slash" (c) So checker just trying to request url like http://host//api/v3/internal/check - with double slash at the left side of "api".
By Administrator on 2013-10-13T04:25:50 (imported from GitLab project)
