Rate limits on Git SSH operations
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
GitLab applies rate limits to Git operations that use SSH by user account and project. When the rate limit is exceeded, GitLab rejects further connection requests from that user for the project.
The rate limit applies at the Git command (plumbing) level. Each command has a rate limit of 600 per minute. For example:
git push
has a rate limit of 600 per minute.git pull
has its own rate limit of 600 per minute.
Because the same commands are shared by git-upload-pack
, git pull
, and git clone
, they share a rate limit.
Configure GitLab Shell operation limit
Git operations using SSH
is enabled by default. Defaults to 600 per user per minute.
- On the left sidebar, at the bottom, select Admin.
- Select Settings > Network.
- Expand Git SSH operations rate limit.
- Enter a value for Maximum number of Git operations per minute.
- To disable the rate limit, set it to
0
.
- To disable the rate limit, set it to
- Select Save changes.
Docs
Edit this page to fix an error or add an improvement in a merge request.
Create an issue to suggest an improvement to this page.
Product
Create an issue if there's something you don't like about this feature.
Propose functionality by submitting a feature request.
Feature availability and product trials
View pricing to see all GitLab tiers and features, or to upgrade.
Try GitLab for free with access to all features for 30 days.
Get help
If you didn't find what you were looking for, search the docs.
If you want help with something specific and could use community support, post on the GitLab forum.
For problems setting up or using this feature (depending on your GitLab subscription).
Request support