CH-UICH-UI

Can't Login?

Fast recovery steps when CH-UI sign-in fails

Use this guide if the login screen appears but sign-in fails, local URL is wrong, or retry windows are blocking access.

Quick Diagnosis

What you seeLikely causeWhat to do
Authentication failedWrong ClickHouse credentialsRetry with the correct username/password for the selected connection
Connection unavailable / UnreachableWrong local ClickHouse URL or offline connectorUpdate local setup and restart CH-UI
Too many login attemptsTemporary lockout after repeated failuresWait retry window (3m, then 5m, then capped at 10m); if URL was wrong, fix setup and restart before retry
No connections configuredEmbedded local connection not reachable/initializedStart CH-UI with explicit local URL and connection name

Recovery From Login Screen

  1. On login, click Can't login? to open the setup sheet directly.
  2. Set:
    • ClickHouse URL
    • Connection Name
  3. Restart CH-UI with one of these commands.

Primary (global install):

ch-ui server --clickhouse-url 'http://127.0.0.1:8123' --connection-name 'My Connection 1'

If running directly from the downloaded binary (no global install):

./ch-ui server --clickhouse-url 'http://127.0.0.1:8123' --connection-name 'My Connection 1'

Docker Recovery

docker run --rm \
  -p 3488:3488 \
  -v ch-ui-data:/app/data \
  -e CLICKHOUSE_URL='http://127.0.0.1:8123' \
  -e CONNECTION_NAME='My Connection 1' \
  ghcr.io/caioricciuti/ch-ui:latest

Environment and Config Alternatives

Environment variables:

CLICKHOUSE_URL='http://127.0.0.1:8123' CONNECTION_NAME='My Connection 1' ch-ui server

Config file (server.yaml):

clickhouse_url: http://127.0.0.1:8123
connection_name: My Connection 1

Then:

ch-ui server -c /etc/ch-ui/server.yaml

Notes

  • Local URL setup does not require Admin access.
  • Admin and multi-connection management are Pro-only capabilities.
  • Setup commands intentionally never include passwords.
  • Credentials are entered only in the Sign in form after restart.
  • Connection display-name priority:
    • --connection-name
    • CONNECTION_NAME
    • server.yaml (connection_name)
    • default Local ClickHouse

On this page