Skip to content
Back

Google OAuth: Cannot re-login after user deletion (400 general_bad_request)

  • 0
  • Self Hosted
  • Flutter
  • Auth
Egor Tabula
24 Mar, 2025, 11:53

Hi! I'm facing a bug with Google OAuth in Appwrite.

🧩 Context: I'm using self-hosted Appwrite 1.6.1 and appwrite: ^15.0.0 (Flutter SDK). I had Google OAuth working properly — I could sign in and create a user via Google in my Flutter app.

Later, I manually deleted that user via Appwrite Console. The user disappeared from the Console UI.

💥 Problem: Now, when I try to sign in again with the same Google account, I get the following error: AppwriteException (400 - general_bad_request)

Additionally:

  • When I try to create a new user with the same email in the Console, it says the user already exists.
  • The user is not listed when I run appwrite users list from the CLI.
  • Attempting password recovery with this email gives user not found.

📌 Extra detail (maybe unrelated): At the same time, my appwrite-worker-deletes container logged this error: You must set a valid security email address (_APP_EMAIL_CERTIFICATES) to issue a LetsEncrypt SSL certificate.

However:

  • _APP_EMAIL_CERTIFICATES is set in my .env
  • SSL certificate is active and valid

📦 Setup:

  • Appwrite self-hosted: v1.6.1
  • Flutter SDK: appwrite: ^15.0.0

🙏 Any idea why this is happening?

Thanks in advance!

TL;DR
Google OAuth login is failing after deleting a user in Appwrite causing a "general_bad_request" error. The user cannot sign in again with the same Google account. The user appears to be deleted but still exists somewhere. The issue might be related to security email setup.
Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more