# Error while creating backup: failed to find CERTIFICATE

**URL:** <https://forums.percona.com/t/error-while-creating-backup-failed-to-find-certificate/23101>\
**Category:** Percona Operator for MongoDB\
**Tags:** mongodb, kubernetes, pbm\
**Created:** [June 26, 2023, 2:10am UTC](https://forums.percona.com/t/error-while-creating-backup-failed-to-find-certificate/23101 "2023-06-26T02:10:27Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Semantic](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/semantic/32/9104_2.png) [@Semantic](https://forums.percona.com/u/Semantic)\
**Post date:** [May 20, 2024, 5:17pm UTC](https://forums.percona.com/t/error-while-creating-backup-failed-to-find-certificate/23101/12 "2024-05-20T17:17:51Z")

</div>

As mentioned previously, those backups actually succeed but are marked with a false-positive error state. I believe that since a real solution would involve codebase changes to this certificate error from surfacing in the first place, here’s a not-so-ideal one, but one you can use right now:

You should install the [edit-status](https://github.com/ulucinar/kubectl-edit-status) kube plugin and edit the state of whatever backup you’d like to use.

```
kubectl edit-status psmdb-backup NAME

```

Update the `status.state` field from `error` to `ready`, which would allow you to use it for a restore.

---

_[View the full topic](https://forums.percona.com/t/error-while-creating-backup-failed-to-find-certificate/23101)._