Back to services

Is GitLab Down? Live status & outage reports

Operational
Last problem:

GitLab outage reports

GitLab common issues

Report a problem

Recent Reports

No reports yet

Service info and troubleshooting

Repository clone fails with timeout error

When cloning large repositories, you might hit a timeout before the operation completes. This happens because the default Git timeout settings aren't generous enough for repos with heavy history. Increase the timeout by running 'git config --global http.postBuffer 524288000' in your terminal. Also try cloning with depth limit using 'git clone --depth 1' to fetch only the latest commit initially, then pull the full history later if needed.

CI/CD pipeline stuck in pending status
  • Check your runner availability in Settings > CI/CD > Runners. If all runners show offline, restart the GitLab Runner service on your machine
  • Verify the runner tags match those specified in your .gitlab-ci.yml file
  • Look for resource constraints: runners might be busy with other jobs. Consider registering additional runners or increasing concurrent job limits in the runner configuration
  • Clear the runner cache by navigating to CI/CD > Pipelines, selecting the problematic pipeline, and manually triggering a retry
Push rejected due to protected branch rules

You're trying to push directly to main or master, but branch protection blocks it. Go to Settings > Repository > Protected Branches and either add yourself to the allowed users list or adjust the merge request requirement. The proper workflow: create a feature branch with 'git checkout -b feature-name', push your changes there, then open a merge request through the web interface.

Web IDE not loading files

The integrated development environment sometimes freezes when opening files. Clear your browser cache and cookies specifically for the GitLab domain. If that doesn't help, disable browser extensions temporarily — ad blockers and privacy tools often interfere with WebSocket connections the IDE relies on. Switch to a different browser to isolate whether it's a browser-specific issue.

Search returns no results for existing code

The search index might be outdated or corrupted. Project maintainers need to trigger reindexing from the admin panel, but regular users can work around this by using grep through cloned repository locally. For immediate needs, GitHub-style search operators work: use 'filename:config.yml' or 'extension:py' to narrow down results and improve accuracy.

Related Services

Check status of Microsoft Microsoft Operational Check status of Nginx Nginx Operational Check status of Outlook Outlook Operational
Thank you for your report. It will be shown in less than 5 minutes. Give us some time for verification and moderation, and thank you for your patience in advance.
Suggest to monitor Help us to improve
Thank you for your suggestion. It will be considered and probably implemented. Give us some time though, and thank you for your patience in advance.