| Application ports | 8123 (HTTP interface), 9000 (native TCP) |
|---|---|
| Admin credential file | sudo cat /var/lib/clickhouse/admin-password |
| Sign in as | default (ClickHouse `default` user; password generated at first boot) |
| Service(s) | clickhouse-server |
| Configuration | /etc/clickhouse-server/config.d/listen.xml (listen_host 0.0.0.0); /etc/clickhouse-server/users.d/default-password.xml (SHA-256 of the generated password) |
| Logs | /var/log/clickhouse-server/clickhouse-server.log; journalctl -u clickhouse-server -f |
| Version | ClickHouse 24.12 (24.12.3.47, official deb stable repository) |
| Platform | Ubuntu 24.04 LTS |
This image generates its admin credential on the VM at first boot — nothing is pre-set. SSH into the VM with the username + key you chose at deploy, then print the generated credential:
ssh <your-username>@<VM-IP>
sudo cat /var/lib/clickhouse/admin-passwordSign in as default (ClickHouse `default` user; password generated at first boot).
This is the password of the ClickHouse `default` user, generated at first boot (stored as a SHA-256 hash in /etc/clickhouse-server/users.d/default-password.xml). Create dedicated users and change it before exposing 8123/9000.
| Symptom | Check | Fix |
|---|---|---|
| `clickhouse-client` says authentication failed for default | sudo cat /var/lib/clickhouse/admin-password | The default user has a generated password on this image: pass it with --password. |
Email support@dcassociatesgroup.com (response within 1 business day) or send a
message via the contact form. Include the offer name, VM size, region, and any log output — sudo journalctl -u <service> -n 100 usually tells the story.