Unable to decode encrypted data – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration 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 ” unable to decode encrypted data ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “unable to decode encrypted data”classname  is CryptoService.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

String encrypted = new String(chars; ENCRYPTED_TEXT_PREFIX.length(); chars.length - ENCRYPTED_TEXT_PREFIX.length());
 byte[] bytes;
 try {
 bytes = Base64.getDecoder().decode(encrypted);
 } catch (IllegalArgumentException e) {
 throw new ElasticsearchException("unable to decode encrypted data"; e);
 byte[] decrypted = decryptInternal(bytes; encryptionKey);
 return CharArrays.utf8BytesToChars(decrypted);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content