Auth0 Lock Component Generates a "Something went wrong" Error When Exceeding 50 Database Connections
Last Updated:
Overview
When an application uses the Auth0 Lock component with Classic Login, Auth0 displays a "Something went wrong" error during login or when testing a database connection via the Try Connection feature. This issue occurs because the targeted application exceeds the limit of 50 enabled database connections. Resolve this issue by creating a new application with fewer enabled connections or by migrating to the New Universal Login.
Applies To
- Auth0
- Classic Login
- Auth0 Lock Component
- Database Connections
Cause
The Auth0 Lock component has a limitation where it cannot support more than 50 enabled database connections for a single application. When an application exceeds this limit and the /authorize request includes a specific connection parameter, and Auth0 generates a JavaScript console error:
Uncaught Error: Error: At least one database, enterprise or social connection needs to be available.
Solution
The connection limit error requires a reduction in database connections or a login migration.
Create a new application with fewer connections or migrate the tenant to New Universal Login by choosing one of the following options:
- Create a new application in the Auth0 dashboard and enable only the required database connections to ensure the total remains under the 50-connection limit.
- Migrate the tenant from Classic Login to New Universal Login, which provides better performance and customization options without this specific Lock component limitation.
What are the differences between Universal Login and Classic Login?
Access the official documentation to compare the features and review the migration steps for the login experiences: