---
title: "Troubleshoot your Connection"
slug: "troubleshoot-your-connection"
updated: 2023-08-08T17:26:21Z
published: 2023-08-08T17:26:21Z
canonical: "docs.preset.io/troubleshoot-your-connection"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.preset.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot your Connection

## Overview

As a Preset Admin, one of your first steps will be connecting a database to Preset so that team members can easily access data and build visualizations. Although we have made the database connection process as intuitive as possible, there are times when an error or misconfiguration may appear.

To help facilitate your success with Preset, we encourage you to read through the best practices and common connection scenarios described below.

---

## Best Practices

### Check #1: Database running?

Confirm that the database is publicly addressable and is currently up and running.

### Check #2: Database supported?

Ensure that your database is supported by Preset. You can view a list of supported databases [here](/v1/docs/connecting-your-data#supported-databases).

### Check #3: Have all connection details?

Preset can connect to a wide variety of databases, many of which require different types of information in order to make a connection. For example, [Google Sheets](/v1/docs/google-sheets-connection) requires a URL with specific sharing settings, [Amazon Redshift](/v1/docs/redshift) requires a host and port, and nearly all databases can be connected to Preset via a SQLAlchemy URI.

Before trying to connect, we recommend that you take some time to read through the relevant connection walkthrough article in order to familiarize yourself with database-specific connection details.

          

#### Connection Walkthrough Articles

          

| [Amazon Athena](https://docs.preset.io/docs/aws-athena) | [Amazon Redshift](https://docs.preset.io/docs/aws-athena) | [Apache Druid](https://docs.preset.io/docs/apache-druid) | [Aurora MySQL (Data API)](https://docs.preset.io/docs/aurora-mysql-data-api) |
| --- | --- | --- | --- |
| [Aurora PostgreSQL (Data API)](https://docs.preset.io/docs/aurora-postgresql-data-api) | [Databricks](https://docs.preset.io/docs/databricks) | [Google BigQuery](https://docs.preset.io/docs/big-query-database) | [Google Sheets (Public)](https://docs.preset.io/docs/google-sheets-connection) |
| [Google Sheets (Private)](https://docs.preset.io/docs/google-sheets-private-connection) | [MySQL](https://docs.preset.io/docs/mysql-connection) | [PostgreSQL](https://docs.preset.io/docs/postgres-connection) | [Snowflake](https://docs.preset.io/docs/snowflake) |
| [Trino](https://docs.preset.io/docs/trino) |

If you'd like to view the SQLAlchemy URI connection strings for all supported databases, please view the [Connection Strings](https://superset.apache.org/docs/databases/installing-database-drivers#supported-databases-and-dependencies) ![external-link_10x10](https://cdn.document360.io/4749ddf8-aa05-4f3f-80e1-07a5d2d0f137/Images/Documentation/external-link_10x10.png) table for detailed information.

---

## Common Errors

### Timeout Errors

A timeout error may occur if you have not properly configured your firewall/network. Preset Cloud currently runs on four regions with the IPs listed below, and those need to be allowlisted so Preset can access your data.

Before starting, please take a moment to allowlist the IPs below based on the region that you're deployed in.

| us-west-2 (us1a) | us-east-1 (us2a) | eu-north-1 (eu5a) | ap-northeast-1 (ap1a) |
| --- | --- | --- | --- |
| 35.161.45.11 | 44.193.153.196 | 13.48.95.3 | 35.74.159.67 |
| 54.244.23.85 | 52.70.123.52 | 13.51.212.165 | 35.75.171.157 |
| 52.32.136.34 | 54.83.88.93 | 16.170.49.24 | 52.193.196.211 |

If you are not sure where your Preset workspace is located, you can refer to the URL on your browser when accessing Preset. It should look like this: https://xxxxxxxx.us2a.app.preset.io/superset..., where us2a means it is in us-east-1.

### Access is Denied

Is the username and password correct? Verify that the login credentials are accurate.

You may be required to enter a username and password when connecting your database to Preset. When entering connection details, please take note of the required **Username** and **Password** fields, such as the ones below from the PostgreSQL → Preset connection process:

![DB_Username_and_Password2](https://cdn.document360.io/4749ddf8-aa05-4f3f-80e1-07a5d2d0f137/Images/Documentation/DB_Username_and_Password2.png)

Alternatively, the user credentials may be included in a SQLAlchemy URI string, such as this one used for a Dremio → Preset connection:

![Dremio_Credentials](https://cdn.document360.io/4749ddf8-aa05-4f3f-80e1-07a5d2d0f137/Images/Documentation/Dremio_Credentials.png)

Some databases may require that access is granted on a per server basis. Check your database manual on how to grant SELECT permissions on your database.

### Database Not Found or Cannot Connect

#### Not found?

If the database cannot be found, then your database or account name may be incorrect.

#### Cannot connect?

Verify that your host and port names are correct during configuration.

Always take note of the **Host**, **Port**, and **Database Name** (or **Account**) fields, such as the ones below used when configuring a MySQL → Preset connection.

![MySQL_Host-Port-DB_Name](https://cdn.document360.io/4749ddf8-aa05-4f3f-80e1-07a5d2d0f137/Images/Documentation/MySQL_Host-Port-DB_Name.png)

          

#### Tip: Dynamic Form Validation

          

- **Host field**: Note that Preset dynamically verifies the name entered in the **Host** field to ensure it can be resolved, so please wait a moment after entering the host name to ensure name resolution.
- **Port field**: Likewise, Preset validates the specified port number to ensure that it can be accessed. After entering a value, please wait a moment while Preset validates the entry.

Remember that some databases require additional information in order to connect, so pay attention to required fields while ensuring accuracy. For example, connections to a [Snowflake](/v1/docs/snowflake) database require **Warehouse** and **Role** fields.

![Snowflake_Warehouse_Role](https://cdn.document360.io/4749ddf8-aa05-4f3f-80e1-07a5d2d0f137/Images/Documentation/Snowflake_Warehouse_Role.png)

          

#### A note on authentication...

          

Some databases require extra steps in order to gather all of the required authentication details necessary to create a connection.

For example, connecting to a [Databricks](/v1/docs/databricks) database requires the creation of an access token while [Google BigQuery](/v1/docs/big-query-database) requires a JSON authentication key generated in the Google Cloud Platform Console.

Remember, if you don't find the answers you need in one of our walkthrough articles, please [submit a support ticket](https://preset.io/support) for assistance.

### SSL Connection is required

If you're having difficulty establishing a connection to your Redshift databse, try to add adding `sslmode=verify-ca` to the ADDITIONAL PARAMETERS field or toggling on SSL in case the database requires an SSL connection. ![image.png](https://cdn.document360.io/4749ddf8-aa05-4f3f-80e1-07a5d2d0f137/Images/Documentation/image%28127%29.png)

---

## Connection Error Messages

### Via dynamic form

When adding a database via the dynamic form, you will receive in-app error messages when an incorrect host is entered:

![Error_Host_Name](https://cdn.document360.io/4749ddf8-aa05-4f3f-80e1-07a5d2d0f137/Images/Documentation/Error_Host_Name.png)

...or an invalid port is entered:

![Error_Port_is_Closed](https://cdn.document360.io/4749ddf8-aa05-4f3f-80e1-07a5d2d0f137/Images/Documentation/Error_Port_is_Closed.png)

### Via SQLAlchemy URI

If connecting to a database using a SQLAlchemy URI, then any returned error messages will appear in the lower right corner of your screen.

Some of the more common errors for [PostgreSQL](/v1/docs/postgres-connection) and [Snowflake](/v1/docs/snowflake) connections include:

### Incorrect database name

**PostgreSQL** ![Error_PostgreSQL_Incorrect_DB_Name2](https://cdn.document360.io/4749ddf8-aa05-4f3f-80e1-07a5d2d0f137/Images/Documentation/Error_PostgreSQL_Incorrect_DB_Name2.png)

**Snowflake** ![Error_Snowflake_Incorrect_DB_Name](https://cdn.document360.io/4749ddf8-aa05-4f3f-80e1-07a5d2d0f137/Images/Documentation/Error_Snowflake_Incorrect_DB_Name.png)

### Incorrect username

**PostgreSQL** ![Error_PostgreSQL_Incorrect_Username](https://cdn.document360.io/4749ddf8-aa05-4f3f-80e1-07a5d2d0f137/Images/Documentation/Error_PostgreSQL_Incorrect_Username.png)

**Snowflake** ![Error_Snowflake_Incorrect_Username](https://cdn.document360.io/4749ddf8-aa05-4f3f-80e1-07a5d2d0f137/Images/Documentation/Error_Snowflake_Incorrect_Username.png)

### Incorrect password

**PostgreSQL** ![Error_PostgreSQL_Incorrect_Password](https://cdn.document360.io/4749ddf8-aa05-4f3f-80e1-07a5d2d0f137/Images/Documentation/Error_PostgreSQL_Incorrect_Password.png)

**Snowflake** ![Error_Snowflake_Incorrect_Password](https://cdn.document360.io/4749ddf8-aa05-4f3f-80e1-07a5d2d0f137/Images/Documentation/Error_Snowflake_Incorrect_Password.png)

### Incorrect username and password

**PostgreSQL** ![Error_PostgreSQL_Incorrect_Username_and_Password](https://cdn.document360.io/4749ddf8-aa05-4f3f-80e1-07a5d2d0f137/Images/Documentation/Error_PostgreSQL_Incorrect_Username_and_Password.png)

**Snowflake** ![Error_Snowflake_Incorrect_Username_and_Password](https://cdn.document360.io/4749ddf8-aa05-4f3f-80e1-07a5d2d0f137/Images/Documentation/Error_Snowflake_Incorrect_Username_and_Password.png)

### Incorrect warehouse and role (Snowflake)

**Warehouse** ![Error_Snowflake_Incorrect_Warehouse](https://cdn.document360.io/4749ddf8-aa05-4f3f-80e1-07a5d2d0f137/Images/Documentation/Error_Snowflake_Incorrect_Warehouse.png)

**Role** ![Error_Snowflake_Incorrect_Role](https://cdn.document360.io/4749ddf8-aa05-4f3f-80e1-07a5d2d0f137/Images/Documentation/Error_Snowflake_Incorrect_Role.png)

---

## Preset Issue Codes

If there is an issue when connecting your database, you will more than likely receive an issue code. Please feel free to view a list of all [Preset Issue Codes](/v1/docs/preset-issue-codes) for your reference — this information may also come in handy in the event that you need to discuss a connection issue with [Preset Support](https://preset.io/support).

---

## What if I Need Help?

If you're still encountering issues when connecting your database to Preset, please let us know via a [Support Ticket](https://preset.io/support) so that we can get you up & running as quickly as possible!