Get back into the console

Every Blink sign-in needs your password and a second factor: a passkey, or a 6-digit code from your authenticator app. Find the message you see below.

“invalid email or password”

1. Check the email address and type the password again. Watch for Caps Lock.
2. Blink has no “forgot password” link. Ask an instance owner to reset your sign-in (see below). They send you a link to choose a new password.
3. If you are sure the password is right, your account may be disabled. Blink gives the same message for a disabled account. Ask someone who manages users to check the Users page; a disabled account shows disabled, and Enable turns it back on.

Your authenticator code is refused (“incorrect code”)

1. Wait for the next code and enter it. Each code works only once, so a code you already used is refused even if it is still on screen.
2. Check that your phone’s clock is set automatically. Codes are based on the time; Blink accepts the code before and after the current one, but not a phone clock that is minutes off.
3. Make sure you are using the Blink entry in your authenticator app, if you have several.

You lost your phone or authenticator

1. On the Two-factor code step, enter one of your recovery codes instead of the 6-digit code. Each recovery code works once.
2. If you have a passkey, click Use your passkey instead.
3. Once you are in, open Account and click New recovery codes under Two-factor authentication. Your old codes stop working. To move to a new phone, have an instance owner reset your sign-in so you can set up two-factor again.
4. If you have no recovery codes and no passkey, ask an instance owner to reset your sign-in.

Reset someone’s sign-in (instance owners)

1. Open Users and expand the person’s row.
2. Click Reset sign-in and confirm. Their password, two-factor and recovery codes are removed and they are signed out everywhere.
3. Copy the link from the Sign-in reset dialog and send it to them. It works once and expires; it is not shown again. If it gets lost, click New invite link on their row.
4. They open the link, choose a new password and set up two-factor again.

If the only instance owner is locked out and has no recovery codes or passkey, contact IZT.

“too many failed sign-ins for this account from your address; try again later”

Too many wrong passwords for this account from your network. By default, wait 15 minutes and try again with the right password. The lockout only applies to your address, so the account still works from elsewhere.

“too many wrong codes for this account; try again later”

Too many wrong two-factor codes. By default, this locks the account on every network for 15 minutes. Wait, then sign in with a fresh code or a recovery code.

“too many attempts; slow down”

Too many sign-in attempts from your address in a short time, or your address was banned for a few minutes after repeated failures. Everyone behind the same office internet connection shares the address. Wait five minutes and try again.

“this address is banned”

An administrator banned your address or network. Every page of your Blink address refuses it until the ban ends or is lifted.

1. Ask an administrator who can still sign in to open Instance › Security › Bans and click Lift next to your address.
2. To keep a trusted network such as your office from being banned by the automatic limits, they can add it to the Allowlist on the same page.

The rate limits behind these messages can be changed under Rate limits on the same page.

“Access to the console from this network is not allowed.”

This is the console’s IP and country rule, not a ban. Your address, or its country, is not on the list of networks allowed to use the console. Signed-in users see the same text on a full page titled Not available from this network.

1. Connect from an allowed network, such as your company VPN or your office, and try again.
2. If you should be allowed from this network, ask an administrator who can still sign in to change Instance › Security › IP and country rules.
3. If nobody can sign in at all, see Nobody can sign in to the console.

More on what a block looks like: Fix a block by an IP or country rule.

“account unavailable”

Your account has been disabled. Ask someone who manages users to check Users and click Enable.

“sign-in session expired; start over”

You took too long between the password and the code. Click Start over and sign in again.

“No passkey of yours works at this address”

Passkeys are tied to the host name you set them up on, and need a trusted HTTPS connection. Open the console on its usual host name, not an IP address, or enter a code instead. See Fix a browser certificate warning.

The recovery kit does not unlock accounts

The recovery kit you saved during first setup (the Recovery key and the Database key backup) recovers your Blink server’s identity and its database key. It does not reset passwords or two-factor. Keep it offline and safe, but use the steps above for sign-in problems.

When to contact IZT

Contact IZT if no instance owner can sign in, or a sign-in error does not match this page. Send the message you see and the time.