On deep-imager, Invalid request after Google sign-in means the OAuth state check failed — restart the full-page flow, do not invent a new email account.
Full-page Google only. Retry from login. Same credits after success.
What does Invalid request mean on the login page?
The Google callback returned, but the state token did not match the session that started Sign in with Google — the product sends you back to /login with that message.
deep-imager uses a full-page redirect to /index.php/api/auth/google, not a small popup. After Google approves, the callback checks state. A mismatch, a cancelled step, or an old tab can surface as Invalid request. Please try again.
The red toast on /login is the English error string prefixed for display. It is not a password typo — password mistakes use the email form path instead.
How do you recover and open the workspace?
Close extra login tabs, click Sign in with Google once, finish the Google screen, and wait for the redirect to / with a token.
Do not bookmark a half-finished callback URL. Start again from the login page button. After success you land on the home workspace — open text to image or image to image with the same credit balance.
New Google accounts still get the first-time 5 credits described in Google sign-in and five credits. Returning users keep their existing wallet.
- Use one browser tab for the OAuth round trip.
- Allow cookies for the deep-imager host so state can be checked.
- If you only use email login, skip Google and use the form or Forgot password.
When should you use email login instead?
When your account was created with email and password, or when Google keeps failing after a clean retry — email login does not use the OAuth state check.
Email and Google are both valid doors to the same product. Mixing them into two accounts splits history. Prefer the method you used at signup. Reset help: forgot password and reset.
Still stuck after one clean Google retry and one email attempt? Write support with the account email — never put passwords or tokens in a generate prompt.
Does a failed Google click spend credits?
No — a failed OAuth return never starts a generate job and never holds a credit.
Credits only move when Generate runs. Plans on pricing from $1/month: Basic 10 credits, Advanced $9.99 for 120, Professional $19.99 for 300. Failed jobs that the product marks failed still refund.
Typical still time after you are signed in is 30 seconds–2 minutes. Read how credits work before a long session.
| Symptom | Likely cause | Next step |
|---|---|---|
| Invalid request toast | OAuth state mismatch | Retry Sign in with Google once |
| Google sign-in failed: … | Google returned error= | Read the suffix; retry or use email |
| Wrong password on form | Email path | Forgot password or correct password |
Start in text to image or image to image, pick a model such as GPT-4o image, then check pricing from $1/month and how credits work before a long run.