Posted on 06/11/26 04:11 am
GitLab code not arriving? Check the number and country code, wait a minute before asking again, and look in filtered texts and your email. 7 fixes, in order.
| You see | It means | Do this |
|---|---|---|
| Code screen, nothing arrives | Slow delivery, filtered texts or a typo | Wait, check spam, resend once |
| "Too many attempts" | Codes are paused for that number | Wait a few hours |
| "Number not supported" or "invalid" | Wrong format, or a number type the app refuses | Re-check format or use a mobile number |
| "Number already in use" | Another account has it | Sign in to that account or use another number |
| "Code incorrect" or "expired" | An older or late code | Request one new code and enter it at once |
GitLab.com may ask new users to verify a phone number or a card before they can run CI/CD pipelines on shared runners. Two-factor supports an authenticator app or a WebAuthn device, with recovery codes.
Some apps refuse VoIP numbers and numbers used on too many accounts. A real mobile number from another carrier often gets through.
Usually a mistyped number, filtered texts, a rate limit, or a number type the app refuses.
A minute or two; after "too many attempts", a few hours.
Many apps offer email; check the code screen for "try another way".
Non-VoIP mobile numbers usually do; VoIP and free public numbers often fail.
You typed an older code or it expired. Use the newest code within a few minutes.
Yes if roaming texts are allowed on your plan; otherwise use Wi-Fi with email or app codes.
Related: GitLab two-factor codes · GitLab phone verification · verification code not received on any app.
Receive SMS online · Non-VoIP numbers · Temporary phone numbers · Free numbers