VyroAI

Loading...

When You Cannot Get In

A reset email that never arrives, a lost authenticator, and the other ways a sign-in goes wrong.

The reset email never arrives

The reset password form always answers the same way — "If that email exists, a password reset link has been sent" — on purpose, so nobody can use it to test which addresses have accounts. If nothing arrives:

Lost your authenticator app

The 2FA dialog says it plainly: "Lost your authenticator app? Contact support — your account cannot be unlocked from this screen." There are no recovery codes, so there is no self-serve way past it. Use the contact form on /support — put in the address the account is registered under, and write login problem in your message. The reply goes to the address you typed in, within 24 hours.

The login code could not be sent

Some sign-ins ask for a 6-digit code emailed to you. If VyroAI cannot send it, you are signed back out, and the message depends on how you signed in: with email and password it reads "Device verification email could not be sent. Please contact support.", and with Google, Discord or GitHub it reads "Could not send your login code. Please contact support." Either one can show a more specific reason from our server instead. That is a mail problem on our side, not your password being wrong. Try again a little later, and tell support if it keeps happening.

The sign-in that never completes

Bouncing back to the login page with a message about cookies means your browser is blocking third-party cookies for vyroai.vip — the sign-in finishes but cannot be stored. Allow them for this site and try again.

The waiting screen that never moves on

A different failure from the cookie one above, and you tell them apart by where you end up.

The cookie case ends: after a few seconds of getting no answer, VyroAI gives up on its own and puts you back on the sign-in page with the message about third-party cookies. Annoying, but finished.

This case never ends. You sit on the Signing you in… card with Setting up your account still marked as in progress, the Taking longer than usual? box appears after a few seconds, and then nothing further happens — no error, no bounce, no app. That is what a dropped connection in the middle of the round-trip looks like: the time limit is only checked once the check comes back, so when the check itself never comes back, the limit never runs and the screen waits.

What to do, in order:

If it happens every time rather than once, use tell us in that same box, or /support and write login problem in your message. Do not sign up again with another address; that makes a second, empty account.

"Login blocked" — your address or your country

Two messages mean the password was right and the sign-in was refused anyway, so there is no point resetting anything:

Neither is something you can fix from the sign-in page, and neither means your account is in trouble — an email about the attempt is sent to you either way. If you are travelling, or on a VPN or a mobile network, turning the VPN off or trying from your usual connection is worth a go first. If that changes nothing, contact support through /support, write login problem in your message and say roughly where you are signing in from.

Your first project refuses to create

Straight after signing up, a project creation can fail. The error dialog explains the likely cause in plain words — a permission issue, a connection problem, a project limit — and offers Retry and Copy Debug Info. Retry usually settles it; if it keeps failing, paste that debug info into a support message.

Getting the password wrong, over and over

Typing the wrong password repeatedly does not lock your VyroAI account and there is no countdown to sit out — nothing in the app puts a timed lock on a sign-in, so the moment you get the password right you are in. Every attempt, right or wrong, is recorded on our side with the internet address it came from.

The limit that really does count attempts is on the 6-digit code emailed to an unfamiliar device. You get five tries: the first wrong code answers "Invalid code. 4 attempts remaining." and each one after it counts down. The fifth wrong code answers "Invalid code. No attempts remaining — please request a new code." — that code is now dead, and any further try gets "Too many failed attempts. Please request a new code." Ask for a fresh code and start that step again — your account is untouched either way.

"Your account is missing a system field"

Signing in or signing up with Google or Discord can end back on the sign-in page with "Your account is missing a system field. The team has been notified — please try again in a minute."

That is our database, not you, and it is not a refused sign-up: the account exists. One field our sign-in service needs was left empty on your row, and it refuses to read a row back with that field empty — so the account was created, it just cannot be opened yet. Filling that field in is part of every update of our database, so it repairs itself, and the same button then signs you in normally.

So do not sign up a second time with another address — you would end up with two accounts and your credits on the first one. Try again a little later, and if it is still happening the next day, contact support through /support and write login problem in your message.

Where to next

19 of 19 in Getting Started · Last checked 17 September 2026 · Previous: Resetting Your Password