You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had this problem when checked application status:
Check GitLab API access: /home/git/gitlab-shell/lib/gitlab_net.rb:122:in read': No such file or directory @ rb_sysopen - /home/git/gitlab-shell/.gitlab_shell_secret (Errno::ENOENT) from /home/git/gitlab-shell/lib/gitlab_net.rb:122:insecret_token'
from /home/git/gitlab-shell/lib/gitlab_net.rb:79:in get' from /home/git/gitlab-shell/lib/gitlab_net.rb:39:incheck'
from /home/git/gitlab-shell/bin/check:11:in `
I googled about this error, and changed version of gitlab-shell into [v2.0.1].
Now, there is no Check GitLab API access: /home/git/gitlab-shell/lib/gitlab_net.rb:122:in read': No such file or directory but I have this Check GitLab API access: FAILED. code: 301.
So I wonder is this version causing gitlab_net.rb:122...? About Check GitLab API access: FAILED. code: 301, I am stilling trying to figure it out. Hope someone can help a little bit. 😄
Oops, I see a PR [here}(https://github.com//pull/261). But the file has not changed yet. I create another PR #281
The text was updated successfully, but these errors were encountered:
When I followed this recipe to installed gitlab-shell using this command:
I had this problem when checked application status:
I googled about this error, and changed version of gitlab-shell into [v2.0.1].
Now, there is no
Check GitLab API access: /home/git/gitlab-shell/lib/gitlab_net.rb:122:in read': No such file or directory
but I have thisCheck GitLab API access: FAILED. code: 301
.So I wonder is this version causing
gitlab_net.rb:122...
? AboutCheck GitLab API access: FAILED. code: 301
, I am stilling trying to figure it out. Hope someone can help a little bit. 😄Oops, I see a PR [here}(https://github.com//pull/261). But the file has not changed yet. I create another PR #281
The text was updated successfully, but these errors were encountered: