## TL;DR
The server rejected the LFS batch upload: LFS is not enabled on the remote, the LFS endpoint is wrong, or the credentials lack LFS scope. Confirm the remote supports LFS, check `git lfs env` endpoints, and re-authenticate. The upload proceeds once the server accepts LFS.

## Error
```text
git lfs push failed: LFS upload rejected by server
```

## Steps
1. Confirm the remote supports LFS: check the hosting provider's settings for the repository. Expected: LFS is enabled; some hosts disable it per repo.
2. Inspect endpoints: run `git lfs env` and verify the endpoint URLs match the remote. Expected: the LFS endpoint points at the right server, not a stale mirror.
3. Re-authenticate: LFS uses its own credential flow; refresh the credential helper or token so the LFS batch request authenticates. Expected: the batch API call returns 200.
4. Check object size and quota: providers cap LFS storage and file sizes. Expected: you are within quota, or you know which cap you hit.
5. Retry the push. Expected: LFS objects upload and the push completes.

## When to use
- `git push` fails specifically on the LFS upload step
- New remotes or migrated repositories
- After credential changes

## When not to use
- Plain git push 413s (non-LFS size issue)
- LFS files downloading as pointers (smudge filter issue)

## Tool compatibility
- Git LFS (`git lfs env`); hosting provider LFS support and quotas

## Variant phrasings
### lfs batch response rejected
The server refused the batch; check LFS enablement and auth on the remote.

### git lfs 403 on push
The credential lacks LFS scope; re-authenticate with a token that covers it.

## Why it happens
LFS uploads go through a separate batch API from the git push, with its own enablement flag, endpoint, and auth scope. Any mismatch (disabled LFS, wrong endpoint, token without LFS rights) rejects the batch while the git half of the push would have succeeded.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Fzd1PG5z3X4bkLDFhM_eGQ
