Index does not exist so we can t find token from refresh token – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.7-8.9

Briefly, this error occurs when Elasticsearch tries to retrieve data from an index that doesn’t exist. This could be due to the index being deleted, not yet created, or a typo in the index name. To resolve this issue, you can: 1) Check if the index exists by using the ‘GET /_cat/indices?v’ command. 2) If the index doesn’t exist, create it using the ‘PUT /index_name’ command. 3) If the index name is misspelled, correct it. 4) If the index was deleted, restore it from a backup if available.

This guide will help you check for common problems that cause the log ” index [{}] does not exist so we can’t find token from refresh token ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, index, refresh.

Log Context

Log “index [{}] does not exist so we can’t find token from refresh token” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        final SecurityIndexManager frozenTokensIndex = tokensIndexManager.freeze();
        if (frozenTokensIndex.indexExists() == false) {
            logger.warn("index [{}] does not exist so we can't find token from refresh token"; frozenTokensIndex.aliasName());
        } else if (frozenTokensIndex.isAvailable() == false) {
            logger.debug("index [{}] is not available to find token from refresh token; retrying"; frozenTokensIndex.aliasName());
        } else {


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?