Documentation
ClickHouse
Connect TableR to ClickHouse over its HTTP interface, with connection fields, SSL/TLS, verifying the connection, and troubleshooting.
ClickHouse is a columnar database for real-time analytics. TableR connects over the ClickHouse HTTP interface; fill the connection form to point at your ClickHouse host.
Overview
TableR talks to ClickHouse over its HTTP interface (default port 8123). It works with a self-hosted server, a container, or ClickHouse Cloud. The columnar engine is built for fast aggregations over very large tables.
- Self-hosted — connect to your ClickHouse host on the HTTP port 8123.
- ClickHouse Cloud / remote — use the provider endpoint and enable SSL/TLS (HTTPS).
- Columnar analytics — optimized for large scans and aggregations rather than single-row lookups.
Before you start
- A reachable ClickHouse host and its HTTP port.
- A user name — this is required.
- The user's password, if the server requires one.
- Optionally, the specific database to open on connect.
- For remote servers: network access to the HTTP(S) port and, usually, SSL/TLS enabled.
Connection fields
These defaults match TableR's ClickHouse connection form. Secrets are written to the operating system keyring, never to plain configuration files.
| Field | Required | Default | Notes |
|---|---|---|---|
| Host | Yes | 127.0.0.1 | Hostname or IP of your ClickHouse host. |
| Port | Yes | 8123 | The ClickHouse HTTP interface port. Use 8443 for the HTTPS interface. |
| Username | Yes | — | The user used to authenticate. |
| Password | No | — | Optional; stored in the OS keyring. |
| Database | No | — | Optional. When empty, the default database is used. |
| SSL/TLS | No | Off | Enable for remote servers (HTTPS); ClickHouse Cloud requires it. |
Connect with the form
- 1Choose ClickHouse
Open the launcher and pick the ClickHouse card.
- 2Enter host and port
Use 127.0.0.1 and 8123 for a local server, 8443 for HTTPS, or your provider's endpoint for a remote one.
- 3Add credentials
Type the username, and the password if required. The password is saved to the OS keyring.
- 4Pick a database (optional)
Set a database to open it directly, or leave it blank to use the default.
- 5Enable SSL/TLS for remote
Turn on SSL/TLS (HTTPS) when connecting to ClickHouse Cloud or any remote server.
- 6Save and connect
Save the profile so it reappears in the launcher, then connect.
SSL/TLS
Local servers usually need no encryption. For anything over a network — and always for ClickHouse Cloud — enable SSL/TLS, which uses the HTTPS interface (default port 8443).
- Off — plain HTTP (local or trusted networks only).
- On — HTTPS to the ClickHouse host.
- ClickHouse Cloud requires TLS; use the HTTPS port.
Verify the connection
Once connected, open a SQL tab and run a quick check:
SELECT version();
SELECT currentDatabase(), currentUser();If both statements return rows, the connection and credentials are working.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Connection refused | Server not running, wrong host/port, or a firewall. | Confirm the server is up and the HTTP port is reachable; re-check host and port. |
| Authentication failed | Wrong username or password. | Re-check the credentials and update the saved password (it lives in the keyring). |
| SSL / HTTPS required | The server requires TLS (typical for ClickHouse Cloud). | Enable SSL/TLS and use the HTTPS port (8443). |
| Database does not exist | The Database field names a database that is missing. | Leave Database empty, or enter one that exists. |