Opster Team
Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.
To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).
This guide will help you check for common problems that cause the log ” Can not access container ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cloud-aws, cloud-azure, container, plugins and repository-azure.

Log Context
Log “can not access container [{}]” classname is AzureStorageServiceImpl.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
try { CloudBlobClient client = this.getSelectedClient(account; mode); CloudBlobContainer blob_container = client.getContainerReference(container); return blob_container.exists(); } catch (Exception e) { logger.error("can not access container [{}]"; container); } return false; } Override
Find & fix Elasticsearch problems
Opster AutoOps diagnoses & fixes issues in Elasticsearch based on analyzing hundreds of metrics.
Fix Your Cluster IssuesConnect in under 2 minutes
Arpit Ghiya
Senior Lead SRE at Coupa