Can not access in container – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.1

Briefly, this error occurs when Elasticsearch, running inside a Docker container, is not accessible due to network issues, incorrect configuration, or insufficient permissions. To resolve this, ensure that the Docker container is running and the network settings are correctly configured. Check the Elasticsearch configuration file for any errors. Also, verify that the user has the necessary permissions to access Elasticsearch. If Elasticsearch is set to run on a specific IP or port, ensure it’s not being blocked by any firewall or security group rules.

This guide will help you check for common problems that cause the log ” can not access [{}] in container {{}}: {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: container, plugins, azure, repositories, repository-azure.

Log Context

Log “can not access [{}] in container {{}}: {}” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

    public boolean blobExists(String blobName) {
        logger.trace("blobExists({})"; blobName);
        try {
            return blobStore.blobExists(buildKey(blobName));
        } catch (URISyntaxException | StorageException e) {
            logger.warn("can not access [{}] in container {{}}: {}"; blobName; blobStore; e.getMessage());
        return false;

    private InputStream openInputStream(String blobName; long position; @Nullable Long length) throws IOException {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?