## Debugging

If you've run an issue that is not listed below, there are several things that are worth keeping in mind while debugging.

- Run `rasactl` with the `--debug` or `--verbose` flag to see more details.
- Your deployment is located in a namespace with the same name as the deployment name. You can use `kubectl` for further debugging, e.g. to check logs for a particular pod.

Example:

```bash
$ rasactl list

CURRENT NAME STATUS RASA PRODUCTION RASA WORKER ENTERPRISE VERSION

\* inspiring-albattani Running 0.0.0 0.0.0 inactive 0.42.1

$ kubectl -n inspiring-albattani get pods

NAME READY STATUS RESTARTS AGE

rasa-x-app-5f4565d579-l9rw8 1/1 Running 0 2m10s

rasa-x-db-migration-service-0 1/1 Running 1 2m10s

rasa-x-duckling-85549fcc5-gqdc4 1/1 Running 0 2m10s

rasa-x-event-service-5dd96d675f-vr9gn 1/1 Running 0 2m10s

rasa-x-postgresql-0 1/1 Running 0 2m10s

rasa-x-rabbit-0 1/1 Running 0 2m10s

rasa-x-rasa-x-5d59dfbb69-jqjvg 1/1 Running 0 2m10s

rasa-x-redis-master-0 1/1 Running 0 38s
```

or

```bash
rasactl logs
```

## Troubleshooting

### `rasactl auth login` returns `Error: exit status 2: gpg: decryption failed: No secret key`

The error message:

```bash
Error: exit status 2: gpg: decryption failed: No secret key
```

can be seen on Linux operating systems in the following cases:

- `pass` is not initialized
- the `GPG_TTY` environment variable is not exported (`export GPG_TTY="$(tty)"`).

Before you start using `rasactl auth login` command be sure that you have installed and initialized `pass`.
In [the README](https://github.com/RasaHQ/rasactl/tree/main#the-auth-login-command) you can find instructions on how to install and configure `pass`.

### `net/http: TLS handshake timeout`

```bash
Get "https://127.0.0.1:55558/api/v1/nodes?labelSelector=node-role.kubernetes.io%!F(MISSING)control-plane%!D(MISSING)": net/http: TLS handshake timeout
```

You can run into the above error if your `kind` node is not responding to requests. Check if a docker container is running (`docker ps -a | grep rasa`) or if the load on your local machine is too high due to running too many applications or containers.