ES snapshot fails on Azure - even though repository is fine and working

[spdoes]

1. Verification status says connected

2. I already did clean up

3. When I try to list the repo in DevTools (in Kibana), it gives me timeout

4. All directories and files permission are fine (I am comparing to another working set up)

5. The logs say that the snapshot was success:

     at java.lang.Thread.run(Thread.java:832) [?:?]

    [2020-12-02T03:50:12,643][INFO ][o.e.c.r.a.AllocationService] [ES_Atlas-ax-es-cluster-node2] Cluster health status changed from [RED] to [GREEN] (reason: [shards started [[.kibana_task_manager_1][0]]]).

    [2020-12-02T03:50:40,839][INFO ][o.e.c.m.MetadataIndexTemplateService] [ES_Atlas-ax-es-cluster-node2] adding template [.management-beats] for index patterns [.management-beats]

    [2020-12-02T06:30:00,006][INFO ][o.e.x.s.SnapshotLifecycleTask] [ES_Atlas-ax-es-cluster-node2] snapshot lifecycle policy [daily-snapshots] issuing create snapshot [daily-snap-2020.12.02-dkeyqkbbtqwaigqcxdx88g]

    [2020-12-02T06:30:00,010][INFO ][o.e.x.s.SnapshotLifecycleTask] [ES_Atlas-ax-es-cluster-node2] snapshot lifecycle policy job [daily-snapshots-1] issued new snapshot creation for [daily-snap-2020.12.02-dkeyqkbbtqwaigqcxdx88g] successfully

    [2020-12-02T06:30:01,450][INFO ][o.e.s.SnapshotsService ] [ES_Atlas-ax-es-cluster-node2] snapshot [elasticsearch-snapshots:daily-snap-2020.12.02-dkeyqkbbtqwaigqcxdx88g/lyhxz79wQT6aDGp-b5b68A] started

    [2020-12-02T06:32:05,492][INFO ][o.e.s.SnapshotsService ] [ES_Atlas-ax-es-cluster-node2] snapshot [elasticsearch-snapshots:daily-snap-2020.12.02-dkeyqkbbtqwaigqcxdx88g/lyhxz79wQT6aDGp-b5b68A] completed with state [SUCCESS]

[warkolm (Mark Walkom)]

Can you post the error you are seeing from Kibana, or ideally Elasticsearch?