Connect to ClickHouse

Connect to ClickHouse over HTTP or HTTPS, including ClickHouse Cloud, with a custom CA, client certificates and an SSH tunnel.

Tablyne talks to ClickHouse through its HTTP or HTTPS interface. Enter an endpoint such as https://host:8443, a user, a password and a database. If you paste a URL that uses ports 9000 or 9440, Tablyne asks you to choose an HTTP(S) endpoint instead, because it does not speak the TCP protocol on those ports.

ClickHouse Cloud is recognized from the host name. Cloud connections, and any connection marked as production, require HTTPS. For a plain http:// address on another machine, Tablyne asks you to tick a box that says the password will travel unencrypted. It suggests HTTPS or an SSH tunnel first.

For TLS you can paste a CA certificate in PEM format. For servers that require a client certificate, paste the certificate and its private key. Tablyne checks the server certificate and reports an untrusted authority or a host name mismatch in plain words. It does not follow redirects to another address, so your credentials are never sent there.

An SSH tunnel is available in the Tunnel section, with its own host key confirmation.

An idle Cloud service can take time to wake up. Tablyne waits up to 90 seconds for it and tells you if it may still be waking. For other servers the connection must open within 8 seconds. When Cloud drops the connection before it answers, the message reminds you to check the service’s IP access list.

The test button shows the server version, the database and the latency. A connection marked read-only adds server-side limits, but write permission still comes from the user you connect with on the server.

Because HTTP has no session, a SET statement does not carry to the next command. Put settings in the query’s SETTINGS clause, or in the run settings panel.