Home › Git

fatal: unable to access ... The requested URL returned error: 403 (Git) — how to fix

remote: Permission to user/repo.git denied to other-user.
fatal: unable to access 'https://github.com/user/repo.git/': The requested URL returned error: 403

Quick fix: Check which account Git uses (remote: Permission ... denied to <user>). Clear the cached credential (git credential reject or Windows Credential Manager / macOS Keychain entry for github.com) and log in again with gh auth login or a token that has repo scope (fine-grained: Contents read and write on that repo).

What it means

HTTP 403 Forbidden: authentication worked (otherwise you'd get 401 / Authentication failed), but the authenticated identity isn't allowed to do this. GitHub usually prints the account it saw:

remote: Permission to acme/api.git denied to old-username.

If that username isn't the one you expect, it's a cached-credential problem. If it is the right user, it's a permissions/scope problem.

Cause 1: cached credentials for another account

Git's credential helper silently reuses the first login it stored for github.com. Find the helper:

git config --show-origin --get-all credential.helper

Clear the stored entry:

printf "protocol=https\nhost=github.com\n\n" | git credential reject

Or by OS:

Next git push prompts again. Use a token as the password, or gh auth login followed by gh auth setup-git.

To use different accounts per repo, include the username in the URL so credentials are stored separately:

git remote set-url origin https://work-user@github.com/acme/api.git
git config --global credential.useHttpPath true   # optional: per-repo credentials

Cause 2: token without write permission

A token can read a repo but not push. Check:

Test what the token can do:

curl -s -H "Authorization: Bearer $TOKEN" https://api.github.com/repos/acme/api | grep -A4 '"permissions"'

"push": true must be there.

Cause 3: you really have no write access

You're a reader on the repo, or it's someone else's project. Either ask for write access, or fork it and push to your fork:

gh repo fork --remote
git push -u origin my-branch

Then open a pull request.

Cause 4: organisation SAML SSO

For orgs with SAML single sign-on, a token must be authorised for the org: GitHub → Settings → Developer settings → Tokens → Configure SSO → Authorize next to the organisation. SSH keys need the same step.

Cause 5: GitHub Actions GITHUB_TOKEN

In workflows, git push with the default token fails with 403 when it is read-only:

permissions:
  contents: write

Also check Settings → Actions → General → Workflow permissions for the repository or org.

Other hosts

Switch to SSH to avoid credential confusion

git remote set-url origin git@github.com:acme/api.git
ssh -T git@github.com     # shows which account the key belongs to

Last updated 2026-11-14.