bit.io works with a lot of different Postgres-compatible tools, but many of those tools have different connection requirements. Connection errors most likely mean that you need to tweak a setting or two, not that the client is incompatible with bit.io. First, check if we have documentation for the tool you're using (in the "Connect to bit.io" section)—we cover specific connection details there.
Otherwise, here are the top three issues with connecting to various clients and how to resolve them.
Incorrectly configured SSL settings are one of the most common reasons for failed bit.io connections.
- Ensure that SSL is enabled on your client
- For some clients, adding
?sslmode=requireto the connection string may be necessary to enable SSL. Connections using the JDBC driver (and tools that use it) may require the ssl property to be set to
- Some clients may be unable to automatically download our server cert. If this is the case you can do so manually here.
By default, database names are on bit.io are formatted
username/database_name. Some clients do not support the default separator '/' that bit.io uses. All of the following separators are valid according to the spec:
/, so if the connection is failing, you may try replace the
username/database_name with a
. for example to yield
As with all Postgres connections, connections to bit.io will timeout after a period of inactivity (60 seconds in our case). If your client does not handle these automatically it may be necessary to enable some retry or keepalive behavior in order to maintain/reestablish connection.
Updated 27 days ago