Troubleshooting Kubby

Common situations in Kubby itself and how to solve them. For problems in your cluster, see the guides below. If your issue is not here, write to support.

A cluster shows "Unreachable"

• Check that your computer can reach the cluster's API address (VPN, firewall).
• If traffic outside the clusters goes through a proxy, set Preferences → Proxy. The Kubernetes API connects with the settings in the kubeconfig.
• If your company uses its own certificate authority, add the CA in Preferences → Proxy.
• If the token has expired, refresh the kubeconfig and edit the cluster.

Monitoring says "No Prometheus found"

• The cluster needs Rancher Monitoring, kube-prometheus-stack or the prometheus chart.
• You need get on services/proxy for the Prometheus service.
• If some panels are empty, those metrics are not collected (for example etcd on managed control planes). The panel explains it.

The Argo CD connection test fails

• "TLS certificate was not accepted": add Argo CD's CA certificate to the instance settings.
• 401 / 403: the token may have expired or the account may lack permission; create a new token.

The Ask Kubby button does not show

Ask Kubby is off by default. In Preferences → External Tools, make sure the connection shows Connected (for CLI subscriptions the tool must be installed and signed in), then turn on Enable Ask Kubby.

The authenticator code is not accepted

Make sure your phone sets its clock automatically; the codes depend on the time. If you cannot reach your phone, sign in with a recovery code. Account and security

Sending information to support

When you write, include your Kubby version (Help → About), your Windows version and the steps to reproduce. Application logs keep the last 5 days; they contain no tokens or passwords.