Not allowed to use HTTP URI uriString Only HTTPS is supported – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 8.2-8.9

Briefly, this error occurs when an Elasticsearch client tries to connect to the server using an unsecured HTTP connection, but the server is configured to only accept secure HTTPS connections. To resolve this issue, you can either change the client’s connection string to use HTTPS or reconfigure the server to accept HTTP connections. However, the latter is not recommended due to security concerns. Always ensure that the correct SSL certificates are in place when using HTTPS.

This guide will help you check for common problems that cause the log ” Not allowed to use HTTP URI [” + uriString + “]. Only HTTPS is supported. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Not allowed to use HTTP URI [” + uriString + “]. Only HTTPS is supported.” class name is JwtUtil.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 // Example URIs w/o host: "https:/"; "https://"; "https://:443"
 throw new SettingsException("Host is missing in HTTPS URI [" + uriString + "].");
 }
 return uri;
 } else if (uriString.startsWith("http")) {
 throw new SettingsException("Not allowed to use HTTP URI [" + uriString + "]. Only HTTPS is supported.");
 } else {
 LOGGER.trace("Not a HTTPS URI [{}]."; uriString);
 }
 }
 return null;

 

 [ratemypost]