ConfigKey must use a consistent scheme http or https – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.4

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when there is inconsistency in the use of HTTP or HTTPS in the configuration key. Elasticsearch requires a consistent scheme for all URLs. To resolve this, ensure that all URLs in your configuration use the same scheme, either HTTP or HTTPS. If some services require HTTPS, it’s recommended to use HTTPS for all to maintain consistency and security. Also, check for typos or incorrect URLs in your configuration.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” [” + configKey + “] must use a consistent scheme: http or https ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “[” + configKey + “] must use a consistent scheme: http or https” class name is HttpExporter.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 httpsHostFound = true;
 }  // fail if we find them configuring the scheme/protocol in different ways
 if (httpHostFound && httpsHostFound) {
 throw new SettingsException("[" + configKey + "] must use a consistent scheme: http or https");
 }  httpHosts.add(httpHost);
 }

 

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?