CODEWITHSUNDEEP
git
Tyler Smith
Tyler Smith

Reputation: 528

GitLab The requested URL returned error: 503

Edit on September 28, 2017. The error description you'll read below makes the problem appear to be GitLab or OS specific. The behavior described can be encountered on any computer behind a proxy while attempting to connect to any internally hosted Git server, whether GitHub, GitLab, Bitbucket, etc... .

I have a RHEL6 server (setup by the corporate server team) that I installed GitLab Community Edition 7.9.2 on following the instructions provided by GitLab here. After following the installation instructions I was able to start the server and login.

I created a group and a project, then I forked into my own account. I can create a file through the GitLab UI and commit it. I'm trying to fetch from my forked project using Git Bash (on Windows 7) and with SourceTree but I'm getting this error:

git -c diff.mnemonicprefix=false -c core.quotepath=false fetch origin fatal: unable to access 'http://server.domain.com/username/project.git/': The requested URL returned error: 503

Most documentation I've found says this is a temporary thing and should be resolved soon. I am the only person using this server, this is the only thing it has installed, and the issue has lasted all day.

I've tried running reconfigure commands on GitLab with no effect. Gitlab or ngenix isn't an installed service so I'm not able to restart them.

Another tidbit here is that I'm a newbie at Linux server management, I haven't touched Linux in 7 years.

Any ideas?

Upvotes: 5

Views: 55195

Answers (3)

Samuel Dauzon
Samuel Dauzon

Reputation: 11324

I encountered an 503 Error and this command helps me to find the element that causes error :

gitlab-rake gitlab:check

It displays the following output (truncated) :

Gitaly: ... default ... FAIL: 14:Connect Failed

Checking Gitaly ... Finished

Checking Sidekiq ...

Sidekiq: ... Running? ... yes
Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Checking Incoming Email ...

Incoming Email: ... Reply by email is disabled in config/gitlab.yml

Checking Incoming Email ... Finished

Checking LDAP ...

LDAP: ... LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Upvotes: 2

CreativeMinds
CreativeMinds

Reputation: 333

This problem is not only created by no_proxy, because it created by git server down issue also.

So When happening this issue first you open and check gitlab in browser.

And check if It shows any error like "503 An internal server error occured". .

The gitlab shows "503" page, this issue create by gitlab server down not in your system.

So you wait some time until the server going up and continue your work.

Upvotes: 8

Tyler Smith
Tyler Smith

Reputation: 528

The problem turned out to be a proxy setting set as a system property. That overrides the gitconfig settings. Once I removed this it was able to work properly.

You can also set an environment variable for no_proxy with your GH url included.

Upvotes: 11

Related Questions