Our Databases data source currently support MySQL, PostgreSQL, and Amazon Redshift databases.
Connecting your SQL database
Run through this list to prepare your database for connecting to Geckoboard.
- Verify that your database is running correctly.
- Ensure your database accept connections from these Geckoboard IP addresses:
- Geckoboard only allows
SELECTqueries, but for extra security, we only accept connections from users that have read-only access to the DB.
- Connections between Geckoboard and your database will be encrypted so your database must have TLS encryption enabled.
If your database doesn't allow SSL connections, is not accessible online, or you want to connect to Microsoft SQL Server or a database we don't currently support, why not try these alternative methods.
To make a new connection to an SQL database, follow these steps:
- On the Connect to Database panel, choose a Database type.
- Type in the Connection name. Give it a memorable name that helps you remember this connection.
- Type in the Host (this could be your Public IP) and Port. By default the port is set to 5432. We cannot connect to a database on localhost (
127.0.0.1). The Host needs to be a publicly accessible address.
- Type in the Database name.
- Type in the database Username and Password
- Click create visualizations from your SQL queries. . If successful, you can start to
Troubleshoot common database connection issues
If you're having trouble connecting to your database, start by running through the list for preparing your database. Then, see if your issue is listed here. If you're still having issues, speak with our Customer Success team.
How do I know if my database is accessible online?
To check if your database is accessible online, run the following command on a computer that’s not logged into your VPN or private network. Replace
your_db_port with the host and port of your database:
- Linux or OSX:
nc -v your_db_host your_db_port
telnet your_db_host your_db_port
If the connection succeeds, your database is accessible online. If it fails, it likely isn’t.
Database connection failed. The permission level of the database user is too high
If you see this error, you are likely connecting with a superuser such as "root". Instead, you should connect using a "read only" user.
Database connection failed. We’re having trouble verifying your connection. Please re-check your details.
This is a generic error, but if you have verified that all connection details provided are correct, it is possible that you are trying to connect an unsupported version of the database. For example, trying to connect a MySQL database that runs on version 5.5.
We currently support MySQL versions 5.6, 5.7, and 8.0.13, PostgreSQL versions 11.1, 10.6, 9.6, 9.5, and 9.4 and the latest version of Redshift.
Can I use SSH tunneling to connect with Databases?
No, Geckoboard doesn't currently support SSH tunneling (also known as post forwarding) for connections to the Database integration.
Option 1 – SQL-Datasets
As an alternative, you may want to try SQL-Datasets.
SQL-Datasets is a command line app developed by Geckoboard to easily connect your database data to Geckoboard via the Datasets API.
The SQL-Datasets functionality ensures your database credentials are maintained exclusively on your system. The app can run on Windows, Mac, or Linux and supports the following Database types:
- Microsoft SQL Server
Option 2 – Allow Geckoboard connections only
Another workaround is ensuring all incoming connections to your database server are disallowed, with the exception of Geckoboard connections. You can do this by whitelisting the following Geckoboard server IP Addresses:
For other options to bring your Database data into Geckoboard, see our guide to connecting your SQL database.