How to resolve "GitLab: API is not accessible" when pushing to a new repository?

Question

we have a locally-hosted Enterprise Edition of GitLab at my place of employment (currently at v7.12.00-ee ceb5083). I can create a repository through the GUI without issue. But when I try to add anything to the repository, I get this error:

D:\ws\testing [master]> git push -u origin master
Counting objects: 3, done.
Writing objects: 100% (3/3), 219 bytes | 0 bytes/s, done.
Total 3 (delta 0), reused 0 (delta 0)
remote: GitLab: API is not accessible
To http://gitlab.ops.cld/duffrw/testing.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'http://gitlab.ops.cld/duffrw/testing.git'

I see in the /var/log/gitlab/gitlab-shell/gitlab-shell.log file that the API isn't responding, and is giving an "Internal Server Error":

E, [2015-07-22T16:05:51.812454 #15110] ERROR -- : API call <POST http://127.0.0.1:8080/api/v3/internal/allowed> failed: 500 => <{"message":"500 Internal Server Error"}>.

A few questions... Where can I go from here? There must some sort of service provider that isn't running. Why not? What's it called? How do I start it?

I checked in /var/log/gitlab/nginx/gitlab_access.log and found these lines, but I didn't see anything interesting:

172.31.201.164 - - [22/Jul/2015:16:05:50 +0000] "GET /duffrw/testing.git/info/refs?service=git-receive-pack HTTP/1.1" 401 0 "-" "git/1.9.5.msysgit.1"
172.31.201.164 - - [22/Jul/2015:16:05:50 +0000] "GET /duffrw/testing.git/info/refs?service=git-receive-pack HTTP/1.1" 401 0 "-" "git/1.9.5.msysgit.1"
172.31.201.164 - duffrw [22/Jul/2015:16:05:51 +0000] "GET /duffrw/testing.git/info/refs?service=git-receive-pack HTTP/1.1" 200 179 "-" "git/1.9.5.msysgit.1"
172.31.201.164 - duffrw [22/Jul/2015:16:05:51 +0000] "POST /duffrw/testing.git/git-receive-pack HTTP/1.1" 200 124 "-" "git/1.9.5.msysgit.1"

There aren't any errors for the push of this repository in /var/log/gitlab/nginx/gitlab_error.log and /var/log/gitlab/nginx/error.log is completely empty.

What am I missing?

Update:

Using the gitlab-ctl tail command is very handy! It revealed a stack trace, which I sent to GitLab and they told me that this was a bug in 7.12.00. It is fixed in 7.13.00.

Answer 1

If using gitlab.com, the server is either being updated or having issues.

You can check https://status.gitlab.com for updates from the GitLab team.

There's also a Twitter account you can follow: https://twitter.com/gitlabstatus