Expected a single certificate; but found – 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.

This guide will help you check for common problems that cause the log ” Expected a single certificate; but found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Expected a single certificate; but found {}”classname  is SamlServiceProviderDocument.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

return (X509Certificate) certificate;
 } else {
 throw new ElasticsearchException("Certificate ({}) is not a X.509 certificate"; certificate.getClass());
 } else {
 throw new ElasticsearchException("Expected a single certificate; but found {}"; certificates.size());
 } catch (IOException e) {
 throw new UncheckedIOException(e);
 } catch (CertificateException e) {
 throw new ElasticsearchException("Cannot parse certificate(s)"; e);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content