# GET \_snapshot/\_status returns 404 "repository\_missing\_exception" even though the repository exists and works
**URL:** https://discuss.elastic.co/t/get-snapshot-status-returns-404-repository-missing-exception-even-though-the-repository-exists-and-works/274098
**Category:** Elasticsearch
**Tags:** snapshot-and-restore
**Created:** [May 26, 2021, 4:41pm UTC](https://discuss.elastic.co/t/get-snapshot-status-returns-404-repository-missing-exception-even-though-the-repository-exists-and-works/274098 "2021-05-26T16:41:51Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@BradVido](https://discuss.elastic.co/u/BradVido)
#### Post date: [May 26, 2021, 4:41pm UTC](https://discuss.elastic.co/t/get-snapshot-status-returns-404-repository-missing-exception-even-though-the-repository-exists-and-works/274098/1 "2021-05-26T16:41:51Z")
I'm using Elasticsearch 6.8.3
The reason I discovered this is because curator calls `GET _snapshot/_status` before it starts doing snapshots, and it is failing with a 404 response.
I've confirmed that the response to that call is indeed:
```auto
{
"error": {
"root_cause": [
{
"type": "repository_missing_exception",
"reason": "[_all] missing"
}
],
"type": "repository_missing_exception",
"reason": "[_all] missing"
},
"status": 404
}
```
But.... this is really strange because **I can successfully backup and restore snapshots** in my repository. I've tried re-creating it with no help.
The repository settings are:
```auto
{
"dev-es6-backup-repository": {
"type": "fs",
"settings": {
"location": "\\\\sanitizedserver\\elasticsearch_backup_repos\\dev-es6-backup-repository"
}
}
}
```
---
### Author:  [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)
#### Post date: [May 26, 2021, 6:25pm UTC](https://discuss.elastic.co/t/get-snapshot-status-returns-404-repository-missing-exception-even-though-the-repository-exists-and-works/274098/2 "2021-05-26T18:25:47Z")
Which version of Curator are you using?
```auto
$ curator --version
curator, version 5.8.4
```
---
### Author:  [@BradVido](https://discuss.elastic.co/u/BradVido)
#### Post date: [May 26, 2021, 6:50pm UTC](https://discuss.elastic.co/t/get-snapshot-status-returns-404-repository-missing-exception-even-though-the-repository-exists-and-works/274098/3 "2021-05-26T18:50:04Z")
Thanks,
I forgot to mention I also updated curator to the latest version to see if it would help. No luck.
`curator.exe, version 5.8.4`
It seems more like an ES problem since it is returning the 404 error.
---
### Author:  [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)
#### Post date: [May 26, 2021, 9:52pm UTC](https://discuss.elastic.co/t/get-snapshot-status-returns-404-repository-missing-exception-even-though-the-repository-exists-and-works/274098/4 "2021-05-26T21:52:13Z")
I would have to deploy Elasticsearch 6.8.3 to see, but I'm _kind of_ leaning towards a change in how Elasticsearch worked with `_all` that came after . Curator has been integration tested against 6.8.15 and does not have this problem.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 23, 2021, 9:53pm UTC](https://discuss.elastic.co/t/get-snapshot-status-returns-404-repository-missing-exception-even-though-the-repository-exists-and-works/274098/5 "2021-06-23T21:53:01Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.