Security limits: attempts, lockouts and cooldowns
A friendly technical rundown of how many attempts you get before a lockout, how long it lasts and why it works that way.
Security limits: behind the "Too many attempts" message
This page is for the curious: you don't need any of this to use Factib, but if you've ever wondered "how many attempts do I have left?" or "how long do I have to wait?", here are the exact numbers and why they're set this way.
The numbers at a glance
| Action | Max attempts | Lockout duration | Counted per |
|---|---|---|---|
| Sign-in password | 5 | 15 minutes | Your account + your IP |
| Verification code (2FA) | 5 | 15 minutes | Your account (any IP) |
| 2FA attempt frequency | 5 per minute | 1 minute | Your IP address |
| Admin panel | 3 | 15 minutes | The IP address |
When you get locked out, the response carries exactly how many seconds remain - the countdown you see isn't an estimate, it's the real time left.
How the time window works
The counter starts on your first failed attempt and runs for 15 minutes from that moment. Later failures stack inside the same window - they don't restart the clock.
So if you miss 4 times at minute 1 and a fifth at minute 14, the lockout lifts at minute 15, not minute 29.
An important detail: this also protects you. Nobody can keep your account locked forever by sending failed attempts - every lockout has a fixed expiry.
What happens when you get it right
A successful sign-in wipes the counter immediately. If you make it in on attempt 4, you start fresh next time.
On the 2FA step the counter follows the window's rhythm: accumulated failures expire when the 15-minute timer does.
The verification session expires too
When your password checks out, Factib opens a 5-minute verification session: the token your browser keeps only lets you try 2FA codes within that window.
The important detail: the verification session (5 min) is shorter than the lockout (15 min). If you got locked out at the code step, once the wait is over you'll need to sign in with your password again - the old verification session is already gone. The app tells you with "The verification session expired" and brings back the password form automatically.
Two different limits (and why)
Two protections work together:
- Per account + IP: 5 password failures from the same account + source IP combination → a 15-minute lockout for that combination. Since the count is per combination, switching IPs hands an attacker a fresh counter - this limit alone doesn't stop a distributed attack. The 2FA code lockout, on the other hand, is per account only, no matter which IP they try from.
- Per IP: 5 attempts per minute on the 2FA form. Stops anyone trying codes at full speed from a single place.
Whichever triggers first is the message you'll see.
And the "Recovery code" field at sign-in?
When you enable two-step verification, Factib generates 8 one-time backup codes. The final step of the setup wizard shows all of them and lets you copy or download them - that's the only time they exist: the server stores only fingerprints (HMAC digests) that can verify a code, never retrieve it.
- Each code goes in the same field as the 6-digit sign-in code and works exactly once - using it deletes it.
- They're your way in when the authenticator phone is lost or replaced.
- Treat them like a spare house key: stored offline, somewhere safe.
- Lost them all or used them up? Turn 2FA off and back on in Settings → Security - every enrollment generates a fresh set.
If you locked yourself out
- Wait for the countdown - there's no way around the lockout, and that's on purpose.
- Check your phone's clock is synced: 2FA codes are time-based; a few seconds of drift produces invalid codes. On Android and iPhone, enable "automatic time".
- No device handy? Use a backup code (you generated them when enabling 2FA). They count toward the same limit, so use them calmly.
- If the issue persists, reach out to support through the usual channel - repeated lockouts you didn't cause could mean someone else is trying to get in.
Where these counters live
Attempts are tracked in Redis, the system's fast in-memory layer - not in the main database. That's why the count survives server restarts and works identically no matter which server instance handles your request.
Interactive tool - available in the app.
For the general overview of how we protect your session, see Your account, protected.