Git http-407-proxy-connect The corporate proxy answered the tunnel request with HTTP 407, demanding authentication.

dev@local: ~/project — git

dev@local~/project$git status

error: http 407 proxy connect

Diagnostics Translation

The corporate proxy answered the tunnel request with HTTP 407, demanding authentication.

waiting for resolution...

MediumVersion Control System

Reviewed for reference consistency: August 11, 2026

Code is Safe

SECURE

Git has paused the operation to protect your code. No data has been lost or corrupted.

What To Know

The CONNECT tunnel through the proxy never opened: the proxy demanded its own credentials, so the repository request never left it.

Where Did It Fail?

Working Tree

Your local files

add

Staging Index

Prepared changes

commit

Local Repo

Commit history

push/fetch

Remote Server

GitHub/GitLab

Git halted to protect the uncommitted files in your active working directory.

Commands That Trigger This

Cloning from an office network whose proxy requires per-user authentication

A CI runner without proxy credentials in its environment

Proxy credentials changed after a password rotation, leaving stored values stale

Technical Background

407 is the proxy's own verdict, distinct from the origin server's opinion: the tunnel to the outside world never opened, so nothing about the repository, its permissions, or its existence was ever evaluated.

Git's HTTP layer recognizes the 407 code specifically — it treats the reply as a proxy-credential rejection and clears the remembered proxy authentication so the next attempt starts fresh. SSH remotes bypass the HTTP proxy entirely, which is why the same repository may work over SSH on the same network.

Underlying Causes

The proxy requires authentication that the environment does not provide

http.proxy is set without embedded credentials where they are required

NTLM or Kerberos proxies reject the authentication scheme Git's HTTP library offered

A stored proxy username and password no longer match after a credential rotation

Frequently Asked Questions

CONNECT is the HTTP method used to open a tunnel through a proxy for TLS traffic; 407 is the proxy refusing to open it until its own authentication succeeds.

No. The failure precedes any contact with the hosting service — the proxy stopped the tunnel before the repository URL was ever evaluated.

Related Git States

authentication-failedMedium

The server rejected your credentials during an HTTPS connection.

could-not-resolve-hostMedium

Your computer's DNS could not find the IP address for the remote repository's domain name.

remote-end-hung-up-unexpectedlyMedium

The connection to the server was closed abruptly before Git finished transferring data.

rpc-failed-curlMedium

The underlying HTTP client (cURL) failed to complete the network request.