Skip to content

Connect Tiger Cloud (Timescale) to Infograph

What it brings in: Every table and view the user can read.

Connect Tiger Cloud (Timescale) 4 steps to set up

What you need

  • A Tiger Cloud service, formerly Timescale.
  • If the service is attached to a peered VPC, an SSH server in that VPC that can reach it.
  • Infograph's sync servers connect from 51.222.152.247.

Your connection string

Each part is one thing you fill in, and each can fail on its own.

Tiger Cloud (Timescale)· Connection string
postgres://:@[service-id].[project-id].tsdb.cloud.timescale.comhost: fix for "We couldn't find that host. Check the host name, then try again.":[port]port: fix for "The host refused the connection. Check the port, and that your database accepts connections from Infograph's address."/tsdbdatabase: fix for "That database does not exist on this server."?sslmode=require
AddressSign inDatabaseSelect a label for its fix

Steps

  1. Allow Infograph's sync servers

    If your project has an IP Allow List attached, open the project's Security settings and add the addresses below.

    51.222.152.247/32

  2. Create a read-only user

    Infograph only reads. Give it its own user so you can see and revoke its access in one place. Run this as tsdbadmin, with your own password. The database is called tsdb. Then use the new user and password in the string.

    CREATE USER infograph WITH PASSWORD '[strong-password]';
GRANT CONNECT ON DATABASE [database] TO infograph;
GRANT USAGE ON SCHEMA public TO infograph;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO infograph;
ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT SELECT ON TABLES TO infograph;

  3. Copy the service's connection details

    Open your service, then Service info, Connect and More details. Use the service's own host and port. Do not use the Connection pooling tab, which breaks syncing.

    postgres://tsdbadmin:[password]@[service-id].[project-id].tsdb.cloud.timescale.com:[port]/tsdb?sslmode=require

  4. Paste it in Infograph and choose your tables

    Open Tiger Cloud in Infograph, paste the string and press Connect. Pick the tables you want and Infograph starts loading them. If the service is in a peered VPC, turn on SSH under Advanced first. Hypertables appear as ordinary tables.

    Allow 51.222.152.247 through your firewall so Infograph can connect.

    Connect

Troubleshooting

Each entry is the message Infograph shows when a connection fails. Open it for the fix.

This host is not reachable from Infograph. Use your database's public address.

A service attached to a peered VPC can only be reached from that VPC. Connect through an SSH server in the VPC, under Advanced.

We couldn't find that host. Check the host name, then try again.

Copy the host from Service info, Connect, More details rather than typing it. It ends in tsdb.cloud.timescale.com.

The host refused the connection. Check the port, and that your database accepts connections from Infograph's address.

Tiger Cloud services use their own port. Copy it from More details, not from the Connection pooling tab.

The server closed the connection. Check that it allows Infograph's address, and whether it requires an encrypted connection.

The server answered, then hung up before Infograph could sign in. Check it allows 51.222.152.247: some hosts close the connection rather than refuse it. If the server accepts only encrypted connections, set SSL Mode to Require under Advanced.

The host did not answer in time. Check the host and port, and that your firewall allows Infograph's address.

If an IP Allow List is attached to the project, add 51.222.152.247 under Security. If the service is in a peered VPC, use an SSH server there.

The username or password was not accepted.

Check the password for tsdbadmin or the user you created. Characters such as @, # or / must be percent-encoded, so @ becomes %40.

Those credentials were not accepted.

Check the user and password in the string. If you created a read-only user, check its name and password.

That database does not exist on this server.

The database is called tsdb. A name of tsdb_transaction comes from the Connection pooling tab, so copy the details from More details instead.

Through an SSH server

Infograph could not reach your SSH server. Check its address and port, and that it allows connections from Infograph's address.

Check the SSH server's public address and port, and that its firewall allows 51.222.152.247 on that port, usually 22.

Your SSH server only offers old encryption settings. Infograph needs a current OpenSSH with an Ed25519, ECDSA or RSA (SHA-2) host key.

Your SSH server only offers old encryption settings. Update OpenSSH on it. It needs an Ed25519, ECDSA or RSA (SHA-2) host key.

Your SSH server refused Infograph's key. Check the key is in authorized_keys for that user.

Add Infograph's public key, shown in the form when you turn on SSH, to ~/.ssh/authorized_keys for the SSH user you entered. Check that user exists and that the file is readable only by them.

Your SSH server's identity changed. If you expected this, trust the new server on the connection.

Infograph remembers your SSH server's key from the first connect, and the server now shows a different one. If you rebuilt or replaced the server, open the connection and press Trust the new server. If you did not, ask whoever runs the server before you trust it.

This connection has not trusted an SSH server yet. Open the connection and use Re-discover streams to trust it.

The connection has not checked your SSH server yet. Open the connection and press Re-discover streams. Infograph then remembers the server's key.

Your SSH server would not forward to the database host. Check the permitopen rule and the database host and port.

The SSH server would not pass the connection on to the database. In authorized_keys, the permitopen rule must name the database host and port exactly as you entered them. In sshd_config, AllowTcpForwarding must not be no. The database must also accept connections from the SSH server, for example in its firewall or security group.