GCC Newspaper
OCTOBER 6, 2026
gcc — Proposed — Sentiment 8 / 10

git pull -> HTTP error 429 (too many requests)

git pull fails with HTTP 429; using 'git://' instead of 'https://' resolves the issue.

Georg-Johann Lay reported receiving an HTTP 429 error when trying to git pull the GCC repository. Josef Melcr suggested using the git:// protocol instead of https://, which resolved the problem for Lay.

In the Thread 3 participants
  1. Georg-Johann Lay proposer

    Reported an HTTP 429 error when attempting to `git pull` the GCC repository.

    “fatal: unable to access 'https://gcc.gnu.org/git/gcc.git/': The requested URL returned error: 429”
  2. Josef Melcr contributor

    Suggested using the `git://` protocol as an alternative to `https://` to bypass the HTTP 429 error.

    “Try 'git://' instead of 'https://'.”
  3. Georg-Johann Lay proposer

    Confirmed that switching to the `git://` protocol resolved the `git pull` issue.

In Details

This discussion concerns a git access issue for the GCC source repository. The user encountered HTTP 429 errors when using HTTPS, a common rate-limiting response from web servers. Switching to the git protocol (git://) bypasses the web server's rate limiting.

Filed Under: gitaccesshttpprotocol