If you’re having trouble connecting to your data warehouse, run through these steps to identify the problem.
SELECT 1query to verify the connection to the data warehouse.
How to detect this: As silly as this sounds, occasionally database servers go down. If you’re using a hosted database service, go to its console and verify that its status is Green. If you have direct access to a command line interface, log in and make sure that it is up and running and accepting queries.
How to fix this: It’s out of the scope of this troubleshooting guide to get your data warehouse server back up. Check with whomever set it up for you!
How to detect this: If you can access the server from a bastion host, or another machine, use
nc on Linux (or your operating system’s equivalent) to verify that you can connect to the host on a given port. Different databases use different ports, but an example for a default PostgreSQL configuration (which listens on port 5432) would be:
nc -v your-db-host 5432`
How to fix this: It’s out of the scope of this troubleshooting guide to change your network configuration. Talk to whomever is responsible for the network your data warehouse is running on.
How to detect this: If you’ve verified that you can connect to the host and port on the data warehouse, the next step is to check your credentials. Again, connecting to a data warehouse depends on your database server software, but for PostgreSQL, the below uses a command-line interface (
psql) to connect to your data warehouse.
psql -h HOSTNAME -p PORT -d DATABASENAME -U DATABASEUSER`
If your credentials are incorrect, you should see an error message letting you know if the database name or the user/password are incorrect.
How to fix this: If the database name or the user/password combination are incorrect, ask the person running your data warehouse for correct credentials.
How to detect this: If you see the error message, “Your question took too long,” something in your setup timed out. Depending on the specifics of your deployment, this could be a timeout in:
How to fix this: Fixing this depends on your specific setup. Here are some potentially helpful resources:
How to detect this: Metabase fails to connect to your data warehouse and the Metabase server logs include the error message
Connections cannot be acquired from the underlying database!
How to fix this: Navigate to the options for your data warehouse and locate the Additional JDBC Connection Strings option, then add
trustServerCertificate=true as an additional string.