Account Temporarily Locked
If you enter a wrong password or a wrong two-factor code several times in a row, Mirox temporarily stops accepting sign-in attempts for your account. This is a protective pause, not a deactivation. Nothing was deleted, nothing was changed, and your data is untouched — the block lifts by itself.
Why This Happens
Your password, and your 6-digit code or your passkey if your account has two-factor authentication (2FA), stand between an attacker and your plant data. Without a limit, someone could simply try password after password, or code after code, until one works. Pausing sign-in after a handful of failures makes that attack impractical, which is why the pause applies to every attempt on your account — including your own.
Wrong codes count like wrong passwords. A wrong 6-digit code — from your authenticator app or from the e-mail — or a wrong backup code on the code screen at sign-in is a failed attempt, exactly like a wrong password. Both are counted together.
You will see a message like "Too many failed attempts. Please try again in 900 seconds." and receive a notification titled Account temporarily locked, naming the location and device the attempts came from.
How Long It Lasts
| Failed attempts within one hour | Sign-in paused for |
|---|---|
| Fewer than 5 | Not paused |
| 5 | 15 minutes |
| 6 or more | 30 minutes |
Two details matter:
- The clock starts at your last failed attempt, not at your first. The countdown shown in the error message is always the authoritative number.
- Attempts made while blocked do not extend the block. Trying again during the pause is harmless — you simply get the same message with less time remaining.
The counter only looks at the last hour. Once an hour passes without a failed attempt, it empties completely and you start fresh.
A sixth mistake costs more than the fifth
Once the pause lifts, your earlier failures are still inside the one-hour window. If your next attempt also fails, you reach six failures and the pause becomes 30 minutes. When the block lifts, make the next attempt count — reset your password rather than guessing again.
Resetting Your Password Does Not Unlock You
This surprises almost everyone, so it is worth stating plainly:
Setting a new password does not lift the block. The pause is tied to the number of recent failed attempts, not to the password itself. If you reset your password while blocked and then sign in with the new one, you will still be refused until the pause expires.
This is not a sign that the reset failed. Your new password is saved and will work. Wait for the countdown to reach zero and sign in again.
Tips
The error you see in this situation is about the block, not about your password. If the message mentions failed attempts or a waiting time, your password is not the problem — the timer is.
The same holds when wrong codes caused the pause: a new password does not help, and neither does a correct code. Wait for the countdown.
What To Do
- Read the waiting time in the error message and wait for it.
- Reset your password in the meantime using Forgot password on the login screen, if you are no longer sure of it. The reset email arrives normally while you are blocked.
- Sign in once when the time is up, with the password you are confident about.
- Check the notification you received. It names the location and device the failed attempts came from. If that was not you, change your password once you are back in.
If You Lost Your Authenticator App
If the pause came from wrong codes because you no longer have your authenticator app, guessing will not get you in. Wait for the pause to end, then:
- Use your passkey if you have one. Nothing changes on your account.
- Use your backup code on the code screen at sign-in. It signs you in and switches the authenticator app off for your account. Set 2FA up again afterwards.
- No backup code and no passkey either? Contact Mirox support. Support can reset your second factor. This signs you out everywhere, and you then sign in with your password and set 2FA up again.
See If You Lose Your Authenticator App.
If You Did Not Cause the Attempts
The notification tells you where the attempts came from. If the location or device is unfamiliar, someone else was trying to reach your account — and the block did its job by stopping them.
Once you are signed in again:
- Change your password to something you have never used elsewhere.
- Enable two-factor authentication, which keeps your account safe even if your password becomes known.
- Review your active sessions and sign out any you do not recognize.
Blocked Without Any Failed Attempts of Your Own
Sign-in attempts are counted per account and per internet connection. A shared connection — an office, a control room, a household — appears to Mirox as a single address. If enough failed attempts come from that connection overall, sign-in is paused for everyone behind it, even for someone who typed their password correctly the first time.
The message in that case refers to your IP address rather than your account. The remedy is the same: wait for the stated time, or use a different connection such as a mobile hotspot.
Getting Help Sooner
If you cannot wait — an outage to investigate, a report due — contact support. A Mirox administrator can lift the block immediately so you can retry, and can send you a password reset link directly if email is the obstacle.
Support can never see your password. If an administrator sets a new one for you, every active session on your account is signed out and you are notified that support did it.
Related
- Authentication — sign-in, two-factor authentication, how long a sign-in lasts, sessions and API tokens
- Setting Up Two-Factor Authentication — enable 2FA, the backup code, and what to do when you lose your authenticator app
- Account Security FAQ — short answers on sign-outs, missing plants and lost authenticators
- Activity & Audit Trail — the record of sign-ins and security events on your account