GitLab remote repository timeouts. Web UI returning 500 & 503 errors

How to Use GitLab
1

Git repository not responding to command-line requests and throwing 500 & 503 errors in web ui.

status.gitlab.com reports all services are green.

When repo does load in webUI, following error message is displayed.
“An error occurred while loading commit signatures”

Command-line timeout response:
Cloning into ‘’…
rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = “transport: Error while dialing dial tcp 10.221.2.132:9999: i/o timeout”
fatal: Could not read from remote repository.

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

Yes, I have the appropriate access rights and repository does exist.

2

Same error here. However the error changes from time to time, some are:

  • Failed to authorize your Git request: internal API unreachable

  • rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = “transport: Error while dialing dial tcp 10.221.2.132:9999: i/o timeout”

  • /opt/gitlab/embedded/service/gitaly-ruby/gitlab-shell/lib/http_helper.rb:79:in `rescue in request’: GitlabNet::ApiUnreachableError (GitlabNet::ApiUnreachableError)

  • remote: GitLab: Push operation timed out
    remote:
    remote: Timing information for debugging purposes:
    remote: Running checks for ref: development
    remote: Checking if you are allowed to push… (4.29ms)
    remote: Checking if default branch is being deleted… (0.12ms)
    remote: Scanning repository for blobs stored in LFS and verifying their files have been uploaded to GitLab… (cancelled after 30002.01ms)

3

GitLab technical issues appear to have been resolved and remote repository is 100% accessible via command-line and web UI.