Troubleshooting and support

Most issues come from the network path between KCM and Kafka, from certificates, or from the reverse proxy in front of KCM. Start with the API log.

Read the logs

# Docker Compose
docker logs -f kcm-api

# Kubernetes
kubectl -n kcm logs deploy/kcm-api -f
kubectl -n kcm logs deploy/kcm-ui -f
kubectl -n kcm get pods,svc,pvc,ingress

Connection tests of clusters, registries and Connect clusters log the full error, including the real certificate error.

A cluster does not connect

# From the API container or pod
nc -vz broker-1.example.internal 9093
openssl s_client -connect broker-1.example.internal:9093 -servername broker-1.example.internal </dev/null

Certificate errors with Schema Registry, Kafka Connect, ksqlDB or Confluent Cloud

These connections verify certificates and host names. If they use a self-signed or private CA certificate, or if KCM runs behind a TLS inspecting proxy, add the root CA in Settings > Trusted certificates. It applies at once, without restart, to every HTTPS call of KCM.

Live views disconnect

kubectl -n kcm describe ingress kcm

SSO sign in fails

"Too many failed sign in attempts"

The sign in is locked for KCM_LOGIN_LOCK_MINUTES (15 by default) after repeated failures. Wait, or sign in from another address if only one address is locked. A user who lost their authenticator app can use a recovery code, or ask an administrator to reset the second factor. See Sign in, 2FA and SSO.

Forbidden errors

"Your license allows..." or additions are blocked

You reached a quota of your edition, or your license allows fewer resources than configured (for example after the trial). Everything keeps running; remove the extra resources named in the banner, or upgrade. See Editions and licensing.

Stored passwords no longer work after a restore or a move

The encryption key pair is not the one that encrypted the database. The API log lists the secrets it cannot decrypt. Restore the key pair saved with the database, or enter those secrets again. See Upgrades and backups.

Get help

When you contact support, include
  • the KCM version (shown in the header of the console) and the edition;
  • Docker Compose, or Kubernetes version and distribution, Ingress controller, helm version;
  • the API log around the time of the failure, without secrets.