If any problems arise or if you are unable to access FusionAuth, consult the FusionAuth log files. In most cases API errors will be written out to the fusionauth-app.log file.
If you need further assistance, please ask a question in the FusionAuth forum or open an issue on Github if you have additional questions. If you have a licensed edition you may open a support request from your FusionAuth Account page.
System log UI
The system logs may be reviewed in the FusionAuth admin UI by navigating to. This feature was added in version 1.16.0. This UI will only render logs for systems that write their logs out to disk. Deployments which write logs to STDOUT, such is the case with Docker, will not be able to review logs through this interface.
The system log UI organizes and renders the most recent 64KB of all logs for all nodes in the deployment. If you need the entire log, use the download action in the upper-right hand corner of UI to download a zip of all logs.
Alternatively, the logs may be accessed directly. The following are the default locations for each of the FusionAuth log files. You may or may not have all of the FusionAuth services installed for your system, so you may not have all of the following logs on your server.
These paths assume the suggested product location of
\fusionauth. This path may be different on your system depending on where you unpacked the zip files.
Note that if you started Windows via Fast Path, the
fusionauth-app.log file will not be created. Instead the services are running interactively and all logging is written to to stdout.
Available since 1.6.0
The event log is a FusionAuth message store designed to capture different types of events that may be necessary to communicate to a FusionAuth developer or admin user.
The event log may contain helpful details to indicate the cause of the failure, or a failure condition you need to be aware of in FusionAuth. See.
While not limited to, generally speaking the event log will contain events or errors related to external systems or asynchronous issues that are difficult to communicate to the API caller or the FusionAuth admin at runtime. While not intended to be an exhaustive list, examples of these types of errors are:
SMTP connection issues
Lambda invocation errors
External identity provider failures or configuration issues
Failure to deliver a webhook event
Be sure to review the Common Errors page to see if there are any fixes for any issues you encounter.