Check for error messages displayed in any of the following locations:
  • Browsers and HTML page responses
  • Developer tools network and console tabs
  • responses
  • Deprecation errors

​
Check browser errors

A HAR file is a JSON formatted log of a web browser’s interactions with a web server. If authentication isn’t working as expected, you can generate and analyze HAR files to find issues.
Before sharing a HAR file with anyone (including Auth0), ensure that you remove or obfuscate all sensitive data, such as:
  • Confidential user information
  • Personal identifiable information (PII)
  • Confidential application information
To learn more, read the following articles on Auth0 Community:

​
Check login screen

The Lock login widget shows error messages for certain types of issues, such as an incorrect username or password. Check the More Information link if you’re using Auth0’s standard error page.

​
Check logs

Auth0 stores log data including Dashboard administrator actions, successful and failed user authentications, and password change requests. You can view the logs in the Dashboard. Some types of errors do not appear in the logs. For example, if an error occurs at a remote , where authentication doesn’t complete and the user is never returned to Auth0, there will not be any entry in logs. You can export Auth0 logs and either store them yourself or automatically push them to external log services. This functionality can help you with data retention requirements, as well as log analysis requirements. You can install and configure an Auth0 Extension to export logs automatically to another provider like Sumo Logic or Loggly. To learn more, navigate to our log streaming solutions in Auth0 Marketplace.
See the Monitoring page for more details on each of the log events that can help you troubleshoot issues.
You can also use the to export logs and store them. There are the two available endpoints, each providing slightly different information.

​
Search all logs /get_logs endpoint

The Search log events endpoint retrieves log entries that match the search criteria you provided. If you do not provide any search criteria, you will get a list of all available entries. You can provide search criteria using the q parameter and retrieve specific fields using the fields parameter. To access the API, you need a Management APIv2 token. This sample request retrieves all logs for successful logins (the event acronym for successful login is s). The list of fields we will retrieve per log entry is: date, description, client_id, and log_id. For details on the search criteria you can use and a list with the event acronyms, see the Search log events endpoint.

​
Get a single log entry /get_logs_by_id endpoint

The Get a log event by ID endpoint retrieves the log entry associated with the provided ID. This sample request retrieves a single log entry with the ID 90020180129170850881585554625888895190928456277777449010.

​
Check logs for deprecation errors

When Auth0 features are deprecated, there may be errors or notices in the tenant logs that show up to indicate that your applications are using the deprecated features. You can search the logs for specific deprecation entries that may indicate that a feature has been deprecated.

​
Rate limits and other errors

Auth0 provides a unique error code for errors reported when the rate limit is exceeded. You should set up automatic scanning of logs to check for rate limit errors so you can proactively address activity that hits rate limits before it causes too much trouble for your users. Auth0 also publishes error codes for other types of errors, and you will find it helpful to scan logs for authentication errors as well as errors from Auth0 Management API calls (Management API error codes are shown below each call in the Management API Explorer). Also note that calling the Management API to retrieve user profile information from within a Rule is a common cause of rate limit errors because such API calls can execute for every login as well as periodic session checks.

​
Check real-time webtask logs error console

You can put console.log() statements into Rules, Hooks, custom database scripts, and Webtasks. The output from those statements is viewable in the Realtime Web Log. If you install the Real-time Webtask Logs extension, you can initiate a view of this log console from the Debug buttons underneath the Rules, Hooks, and custom DB script editor windows, or from the webtask console for webtasks.

​
Learn more