Cannot Login with Database Connection Users — “Oops!, something went wrong” on /u/login

[harshiniadditional]

Hi team,

I’m experiencing an issue where database-created users cannot log in at all, even though user creation works perfectly.

Tenant Details

• Region: US

• Connection: Username-Password-Authentication (Database)

• App Type: Regular Web Application

Issue Summary

I am able to successfully create users through the Management API:

POST https://dev-****************.us.auth0.com/api/v2/users

Users are created correctly, appear in the Dashboard, and receive verification emails.

However, none of these users are able to log in, even after verification.

Error on Login Page

When visiting:

https://dev-****************.us.auth0.com/u/login

I consistently get:

“Oops!, something went wrong. There could be a misconfiguration in the system or a service outage.”

This happens:

• even after creating multiple test users

• even after enabling the database connection for the application

• even after creating a new Regular Web Application

• even after verifying emails

• even after switching browsers / incognito

Important Notes

• Users are created successfully (JSON response attached below).

• Passwords meet complexity rules.

• Admin dashboard login works fine.

• The issue affects only end-user authentication.

• The connection “Username-Password-Authentication” is enabled for the application.

User Creation Example

{
  "email": "sampleuser@gmail.com",
  "password": "Hn3!cR7@pL95",
  "connection": "Username-Password-Authentication",
  "name": "sample user",
  "blocked": false
}

Login attempt with this user → same “Oops! something went wrong” page.

Questions

1. Is /u/login the correct login endpoint for database users?
   Or should I be using a different login route for testing user credentials?

2. Is there any tenant-level restriction preventing login for database users?

3. Are there known misconfigurations that typically cause /u/login to always return the generic “Oops!” error?

4. Does a Regular Web Application require additional configuration for login to work?
   (Callback URLs, Allowed Web Origins, etc.)

What I’ve Already Tried

• Creating multiple new users

• Verifying emails

• Resetting passwords

• Creating a new application

• Re-enabling the Database Connection

• Checking built-in login settings

• Clearing cookies / trying incognito

• Testing from different devices

All attempts end in the same Server Error page.

[nik.baleca]

Hi @harshiniadditional

Welcome to the Auth0 Community!

1. Is /u/login the correct login endpoint for database users?
   Or should I be using a different login route for testing user credentials?

Yes, the initial redirect would be to the /authorize endpoint of your application which then redirect to the /u/login endpoint for your Universal Login.

2. Is there any tenant-level restriction preventing login for database users?

Not necessarily, you can restrict database access to certain users, however, if you are using the basic database for your application, it should also be the one configured as the default directory.

3. Are there known misconfigurations that typically cause /u/login to always return the generic “Oops!” error?

There can be numerous ones, however, is the message you have received the only thing included or did it provide additional ones in the network trace or Auth0 logs?

4. Does a Regular Web Application require additional configuration for login to work?
   (Callback URLs, Allowed Web Origins, etc.)

Any type of application would require you to have the proper callback URLs or Allowed Web Origins depending if you are testing using the specific/authorize of the application or using a local environment. Could you provide me more information about how are you testing the login process of your users? Also, have you tried to create a user through the Dashboard instead of the Management API to see if you receive the same error?
For me to be able to find out more about your tenant configuration, an you DM me the tenant name?

Kind Regards,
Nik