Fatal - HTTP request failed

Fatal: HTTP request failed means your request to our Git server was not received, which is indicative of a problem with your network connectivity (your computer is not able to contact the server), incorrect URL formatting, or, if you are using a proxy server on your company network, you have not set a PROXY server in your Git client.

It could also be intermittent connectivity, or a firewall\proxy issue at your company. A firewall could be preventing communications or you may be required to use a proxy server for Git operations, depending on your network operator’s security preferences. It is possible that your companys firewall is blocking Git, that URL, or both.

Check with your network operator for their policy on Git protocol over HTTPS, and see if that is supported or requires a proxy server.

Another troubleshooting step is to check… * Do all employees at my company experience the same problem on all machines connected to my company’s network? * Does the same error occur outside the company network and while connected to another network with public Internet access? * Which version of Git is in use * Which OS is running Git (Windows, Linux, etc.) * Are you using the exact URL that is shown on ChipCode for the git repository?

Embedding your credentials in the URL Do not embed your credentials in the Git URL. That will cause the lookup to fail as well as a fatal HTTP request failed. If you want to cache your credentials for automation, refer to Avoiding Entering Username and Password for Git Operations for instructions.

Network Connectivity Causes * Connection time-out while accessing * Failed connect to * Couldn’t resolve host while accessing * fatal: unable to access * error: Operation timed out after X milliseconds with X out of X bytes received while accessing * error: Could not fetch origin