Is GitLab down today?

How to Contact GitLab Technical Support?

- Support Portal at https://support.gitlab.com;

- Documentation at https://docs.gitlab.com;

- Community forum at https://forum.gitlab.com;

- Issue tracker at https://gitlab.com/gitlab-org/gitlab/issues;

- X (Twitter) @gitlabstatus for status;

- Status page: https://status.gitlab.com.

Latest News and Current Information:

- Official Website - https://about.gitlab.com;

- GitLab.com - https://gitlab.com;

- Documentation - https://docs.gitlab.com;

- Blog - https://about.gitlab.com/blog;

- X (Twitter) - https://twitter.com/gitlab;

- Status - https://status.gitlab.com;

- YouTube - https://www.youtube.com/gitlab;

- LinkedIn - https://www.linkedin.com/company/gitlab-com;

- Facebook - https://www.facebook.com/gitlab;

- Forum - https://forum.gitlab.com.

GitLab Outage: DevOps Platform Service Down

Service disruptions manifest as GitLab not loading, repositories inaccessible, dashboard blank, login errors, or complete platform unavailable.

- Check GitLab status at https://status.gitlab.com;

- Refresh browser page completely;

- Verify stable internet connection;

- Clear browser cache and cookies;

- Try different browser (Chrome/Firefox);

- Wait 15-30 minutes during maintenance;

- Check firewall not blocking GitLab;

- Switch between WiFi and mobile data;

- Try incognito/private browsing mode;

- Monitor @gitlabstatus for updates.

Repository or Project Problem: Cannot Access GitLab Projects

Repository access issues include projects not loading, "404 not found" errors, files missing, or repositories displaying blank.

- Refresh page to reload project;

- Check project visibility settings;

- Verify account has access permissions;

- Clear browser cache completely;

- Check project not deleted/archived;

- Verify group membership active;

- Try GitLab CLI instead;

- Check project URL correct;

- Verify branch exists;

- Contact project owner for access.

Login or Authentication Issue: Cannot Access GitLab Account

Authentication problems include login failing, password rejected, two-factor authentication errors, SSH key issues, or account locked.

- Verify username and password correct;

- Use "Forgot password" for reset;

- Check 2FA code entering correctly;

- Verify SSH keys configured properly;

- Clear browser cookies and retry;

- Try personal access token instead;

- Check account not suspended;

- Verify email address confirmed;

- Remove and re-add SSH key;

- Submit ticket for account recovery.

Push or Pull Fault: Git Operations Failing on GitLab

Git operation issues include push rejected, pull failing, "permission denied" errors, merge conflicts, or authentication errors.

- Check repository permissions granted;

- Verify SSH/HTTPS credentials correct;

- Update Git to latest version;

- Check protected branch rules;

- Verify remote URL configured;

- Check file size limits (repository quota);

- Clear Git credential cache;

- Verify network allows Git protocol;

- Contact admin about access rights;

- Review push rules configured.

CI/CD Pipeline Problem: GitLab CI/CD Not Running

Pipeline issues include jobs not triggering, runners offline, builds failing, or workflow syntax errors.

- Check .gitlab-ci.yml syntax valid;

- Verify CI/CD enabled in project;

- Check runner availability and tags;

- Review pipeline logs for errors;

- Verify variables/secrets configured correctly;

- Check runner quota not exceeded;

- Test pipeline locally if possible;

- Verify trigger conditions correct;

- Check required jobs passing;

- Update CI/CD configuration syntax.

Merge Request or Code Review Problem: MRs Not Working

Merge request issues include MRs not creating, reviews failing, merging blocked, or approval rules broken.

- Check branch up to date;

- Verify required approvals completed;

- Check pipeline status passing;

- Review merge request rules;

- Verify no merge conflicts;

- Check required checks configured;

- Update MR branch from target;

- Verify permissions to merge;

- Check draft/WIP status;

- Review merge train settings.

Issue Tracking or Board Fault: GitLab Issues Not Working

Issue management problems include issues not creating, labels missing, milestones broken, or boards not updating.

- Refresh page to reload issues;

- Check issue template used correctly;

- Verify permissions to create issues;

- Check filters applied on view;

- Clear browser cache;

- Verify board automation rules;

- Check issue not already exists;

- Review project settings;

- Verify labels exist in project;

- Try different browser.

Pages or Static Site Problem: GitLab Pages Not Deploying

GitLab Pages problems include site not publishing, 404 errors, build failing, or custom domain not working.

- Check Pages enabled in project;

- Verify CI/CD job for Pages;

- Review build/deployment logs;

- Check custom domain DNS settings;

- Wait for deployment completion;

- Verify HTTPS enforcement settings;

- Check public folder structure;

- Clear browser cache for site;

- Verify Pages quota not exceeded;

- Check .gitlab-ci.yml Pages job.

Container Registry or Package Problem: Registry Not Accessible

Registry issues include Docker images not pushing, packages failing to upload, registry authentication errors, or storage quota exceeded.

- Verify registry enabled in project;

- Check Docker login credentials;

- Review registry quota limits;

- Verify token permissions sufficient;

- Check image tag format valid;

- Clear Docker cache locally;

- Verify network allows registry access;

- Check storage limits not exceeded;

- Review registry cleanup policies;

- Test with smaller images first.

Wiki or Documentation Issue: GitLab Wiki Not Working

Wiki functionality problems include pages not saving, formatting broken, attachments failing, or history missing.

- Refresh wiki page;

- Check wiki enabled in project;

- Verify edit permissions granted;

- Clear browser cache;

- Try different markup syntax;

- Check file attachments size limits;

- Verify wiki not locked;

- Review page history for changes;

- Try cloning wiki repository;

- Check special characters in titles.

Group or Namespace Problem: GitLab Groups Not Accessible

Group management issues include members not adding, permissions wrong, subgroups broken, or settings not saving.

- Verify group owner permissions;

- Check member invitation sent;

- Review role assignments;

- Verify subscription current;

- Check group plan limits;

- Review group security settings;

- Check SAML/SCIM configuration;

- Verify member accepts invitation;

- Review audit log for changes;

- Contact GitLab billing support.

Runner or Executor Fault: GitLab Runners Not Connecting

Runner problems include runners offline, registration failing, jobs not picking up, or executor errors.

- Check runner service status;

- Verify runner token correct;

- Review runner configuration file;

- Check runner tags match jobs;

- Verify network connectivity to GitLab;

- Check runner quota available;

- Review runner logs for errors;

- Update runner to latest version;

- Verify executor configured properly;

- Re-register runner if needed.

Snippets or Code Sharing Issue: GitLab Snippets Not Working

Snippet functionality problems include snippets not creating, visibility wrong, embedding broken, or syntax highlighting missing.

- Refresh snippet page;

- Check snippet visibility settings;

- Verify account logged in;

- Clear browser cache;

- Try different programming language;

- Check embed code syntax;

- Verify snippet not deleted;

- Review snippet permissions;

- Try different browser;

- Check syntax highlighting supported.

API or Webhook Problem: GitLab API Not Responding

API issues include requests failing, rate limiting, authentication errors, webhook not firing, or integration broken.

- Check API rate limits;

- Verify personal access token valid;

- Review API endpoint correct;

- Check webhook payload delivery;

- Verify token scopes sufficient;

- Test API with curl/Postman;

- Check API version compatibility;

- Review webhook secret configured;

- Verify firewall allows webhooks;

- Check integration logs.

Self-Managed or Instance Issue: GitLab Self-Hosted Problems

Self-hosted GitLab problems include instance down, upgrade failing, database errors, or performance degradation.

- Check GitLab service status: `gitlab-ctl status`;

- Review logs: `gitlab-ctl tail`;

- Verify system resources sufficient;

- Check database connectivity;

- Review upgrade documentation;

- Verify dependencies updated;

- Check disk space available;

- Review configuration changes;

- Restart services: `gitlab-ctl restart`;

- Consult GitLab admin documentation.