# How to troubleshoot "could not detect velero" error

**URL:** <https://community.replicated.com/t/how-to-troubleshoot-could-not-detect-velero-error/875>\
**Category:** Troubleshooting\
**Created:** [July 19, 2022, 12:44pm UTC](https://community.replicated.com/t/how-to-troubleshoot-could-not-detect-velero-error/875 "2022-07-19T12:44:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kevinr](https://avatars.discourse-cdn.com/v4/letter/k/da6949/32.png) [@kevinr](https://community.replicated.com/u/kevinr)\
**Post date:** [July 19, 2022, 12:44pm UTC](https://community.replicated.com/t/how-to-troubleshoot-could-not-detect-velero-error/875/1 "2022-07-19T12:44:52Z")

</div>

I’m trying to run “kubectl kots velero ensure-permissions” to inform KOTS where Velero is located on my cluster. However the command always returns:

Error: could not detect velero in ‘cluster-629e09268fb44b8f0499963a’ namespace

Kotsadm is installed in the “kots” namespace, Velero is installed in the “cluster-629e09268fb44b8f0499963a” namespace. The command I’m running is:

kubectl kots velero ensure-permissions --velero-namespace cluster-629e09268fb44b8f0499963a --namespace kots

I’ve looked at the checks [here](https://github.com/replicatedhq/kots/blob/main/pkg/snapshot/velero.go) and added the “component” and “deploy” labels to the velero & restic pods, but this didn’t make a difference.  
Is there any way to enable more verbose debugging output from “kubectl kots”, to figure out why it’s not detecting velero?

---

<div class="post-metadata">

**Author:** ![salahalsaleh](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/salahalsaleh/32/464_2.png) [@salahalsaleh](https://community.replicated.com/u/salahalsaleh)\
**Post date:** [July 21, 2022, 8:58pm UTC](https://community.replicated.com/t/how-to-troubleshoot-could-not-detect-velero-error/875/2 "2022-07-21T20:58:15Z")

</div>

Hi Kevin!

Could you please validate that there is a `backupstoragelocation` object named `default` in the `cluster-629e09268fb44b8f0499963a` namespace?

Basically, check the output of the following command:

```bash
kubectl get bsl -n cluster-629e09268fb44b8f0499963a

```

The other thing I would recommend validating is that the user running the command should have access to the `cluster-629e09268fb44b8f0499963a` namespace.

Let me know if that helps.

Salah - Senior Software Engineer @ Replicated

---

<div class="post-metadata">

**Author:** ![kevinr](https://avatars.discourse-cdn.com/v4/letter/k/da6949/32.png) [@kevinr](https://community.replicated.com/u/kevinr)\
**Post date:** [July 22, 2022, 10:23am UTC](https://community.replicated.com/t/how-to-troubleshoot-could-not-detect-velero-error/875/3 "2022-07-22T10:23:04Z")

</div>

Ah indeed, ensuring a BSL called `default` exists, solves the problem. Thanks for the tip!