Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Git Error: The requested URL returned error: 504 Gateway Timeout while accessing http://

I am using a VM provisioned by my company's internal cloud (KVM) - RHEL 6.4.

I am able to clone external repositories from the internet. Yet, I cannot figure out how to clone internal repositories on my company's intranet.

At first I didn't set the http_proxy or https_proxy and received this error:

error: The requested URL returned error: 401 Authorization Required while accessing http://....

After setting http_proxy and https_proxy, I now receive this error after waiting about 60 seconds:

error: The requested URL returned error: 504 Gateway Timeout while accessing http://...

I can clone this repo find from my laptop, just not the VM

Any ideas on where I should look?

Thanks.

like image 279
Matthew Moisen Avatar asked Jan 13 '14 07:01

Matthew Moisen


People also ask

What causes a 504 Gateway Timeout?

A 504 Gateway Timeout error indicates that the web server is waiting too long to respond from another server and “timing out.” There can be many reasons for this timeout: the other server is not functioning properly, overloaded, or down. The other server need not always be external (e.g. CDN, API gateway).

What do you mean by Gateway Timeout?

The 504 (Gateway Timeout) status code indicates that the server while acting as a gateway or proxy, did not receive a timely response from an upstream server it needed to access in order to complete the request. The error may be a temporary occurrence due to too much traffic toward the server or site.

How does node js handle 504 Gateway Timeout?

I added this code to the app. js : var connectTimeout = require('connect-timeout'); var longTimeout = connectTimeout({ time: 600000 }); app. use(longTimeout);


2 Answers

use this in .gitconfig file then this problem will resolved.

- [http]      proxy = http://127.0.0.1:8087      sslVerify = false 

OR git config --global http.proxy ''

like image 59
Muhammad Tariq Avatar answered Oct 03 '22 06:10

Muhammad Tariq


The 504 status is most likely because you're trying to access an internal server through the proxy so I don't think you should set the proxy but instead focus on the 401 status since that most likely comes from the server hosting the repositories.

  • Do you have anonymous access to the internal repositories?

  • Are you cloning them in the same way, i.e. using HTTP on both your laptop and on the server, or are you using SSH on the laptop and HTTP on the server?

  • Do you have any credentials stored on your laptop?

like image 30
Raniz Avatar answered Oct 03 '22 06:10

Raniz