< Documentation Home

---

Troubleshooting Tips

If you experience any issues using Nadrama, please reach out to us via the Console “Help / Feedback” link or chat icon on the bottom-right of the Console. If you are unable to access that, visit our chat page (though the former is preferred).

Connectivity issues

Several factors in your cloud provider account configuration may prevent cluster VMs from connecting to Nadrama servers. For example, on AWS you may have a network policy which prevents an EC2 instance from connecting to Nadrama servers.

Connectivity is required for your VMs to register with the Nadrama control plane, for them to be issued with valid cluster TLS certificates, report health metrics, and to establish a secure tunnel for your Kubernetes API server.

On AWS, you should check your EC2 instance system log:

1. Go to your list of EC2 instances and check the box next to one with a Name prefix like <your-cluster-slug>-knc

2. Click the Actions button, then under Monitor and troubleshoot select Get system log.

3. Scan through the system log for any errors, which may provide hints into what is causing connectivity issues. Please send a copy of any logs to us for support.

Unable to connect to Kubernetes API

After you have successfully run nadrama cluster login <your-cluster-slug> on your desktop/laptop, if you encounter issues connecting to the Kubernetes API (e.g. errors, strange HTML response, etc.) check that the tunnel is online by visiting https://<your-cluster-slug>.k8s.cluster.env in your browser.

If the cluster tunnel is offline, it is likely due to a Connectivity issue - see above for troubleshooting tips.

Known issues

macOS unable to run the CLI as it is not verified/signed

Please install our CLI via homebrew for the time-being.