# Elasticsearch -Azure Repository - stopped working suddenly

**URL:** <https://discuss.elastic.co/t/elasticsearch-azure-repository-stopped-working-suddenly/138045>\
**Category:** Elasticsearch\
**Created:** [June 29, 2018, 11:42pm UTC](https://discuss.elastic.co/t/elasticsearch-azure-repository-stopped-working-suddenly/138045 "2018-06-29T23:42:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Karthik\_Ramachandran](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@Karthik\_Ramachandran](https://discuss.elastic.co/u/Karthik_Ramachandran)\
**Post date:** [June 29, 2018, 11:42pm UTC](https://discuss.elastic.co/t/elasticsearch-azure-repository-stopped-working-suddenly/138045/1 "2018-06-29T23:42:53Z")

</div>

Azure snapshots suddenly started failing with Gateway error. It was working fine for longer time, but stopped with below error. Got this error on \_cat snapshots.

{  
"statusCode": 504,  
"error": "Gateway Time-out",  
"message": "Client request timeout"  
}

Tried to access the storage account using curl/SAS from the master node explicitly and it do access without issues.

When I issue \_verify again, it fails as below from the master node , and against cluster it gives gateway error as above.

............ERROR when I ssh into master and issue \_verify explicitly against the node.....................  
{"error":{"root\_cause":[{"type":"repository\_verification\_exception","reason":"[......] path [snapshots] is not accessible on master node"}],"type":"repository\_verification\_exception","reason":"[....] path [snapshots] is not accessible on master node","caused\_by":{"type":"i\_o\_exception","reason":"Can not write blob master.dat-temp","caused\_by":{"type":"storage\_exception","reason":"Operation could not be completed within the specified time."}}},"status":500}

Tried to see which key it is using to access Azure, but it is in keystore so not sure how to get the value. Tried to base64 decode on the Auth header but not sure if it is right approach as the encryption logic may be diff 🙂

Any guidance would be helpful.

---

<div class="post-metadata">

**Author:** ![Karthik\_Ramachandran](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@Karthik\_Ramachandran](https://discuss.elastic.co/u/Karthik_Ramachandran)\
**Post date:** [July 24, 2018, 12:34am UTC](https://discuss.elastic.co/t/elasticsearch-azure-repository-stopped-working-suddenly/138045/2 "2018-07-24T00:34:00Z")

</div>

Not getting gatework timeout on \_cat now, instead getting empty result. BUt still getting repository verification error. Not sure of the reason. Ensured that the storage account exists..

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 21, 2018, 12:36am UTC](https://discuss.elastic.co/t/elasticsearch-azure-repository-stopped-working-suddenly/138045/3 "2018-08-21T00:36:47Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.