| title |
|---|
Troubleshooting guides |
Problems, their causes, how to detect them, and how to fix them.
- Running the Metabase JAR.
- Running Metabase on Docker.
- Using or migrating from an H2 application database.
- I can't connect to a database.
- I can't see my tables.
- The data in Metabase doesn't match my database.
- My database is slow.
- My connection or query is timing out.
- I can't save my question or dashboard.
- I can't view or edit my question or dashboard.
- My visualizations are wrong.
- My dashboard is slow or failing to load.
- My SQL question doesn't work.
- The dates and times in my questions and charts are wrong.
- My filters don't work.
- My linked filters don't work.
Metabase will log errors, both on the server and in the browser console, depending on where the error occurs, which can help you track down an issue. Administrators will have access to the server logs, and everyone with a browser can open the developer tools to see the console logs.
Accessing the Metabase server logs: You can look for the logs that Metabase leaves on the server's file system (or wherever else you collect logs). If you're logged into Metabase with an Admin account, you can also access the logs by going to the top right of the screen and clicking on the gear icon > Admin settings > Troubleshooting > Logs. Check out How to read the server logs.
Checking for Javascript console errors: Metabase will send debugging information and errors to your browser's developer console. To open the developer console, follow the instructions for your web browser:
For tutorials that walk you through how to use Metabase features, check out Learn Metabase.
To see if someone else has run into a similar issue, check out our forum on Discourse.
Metabase adds new features and squashes bugs with each release. Upgrading to the latest and greatest may resolve your issue. If you're using Metabase Cloud, we'll handle the upgrades for you. You can checkout the release notes to see what's new.