Briefly, this error occurs when Elasticsearch is unable to parse the provided HTTPS URI due to incorrect syntax or format. This could be due to missing ‘https://’, incorrect port number, or invalid characters. To resolve this issue, ensure that the URI is correctly formatted, all necessary components are included, and there are no invalid characters. If the URI includes a port number, verify that it is correct. Also, check if any special characters in the URI are properly encoded.
This guide will help you check for common problems that cause the log ” Failed to parse HTTPS URI [” + uriString + “]. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “Failed to parse HTTPS URI [” + uriString + “].” class name is JwtUtil.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
if (uriString.startsWith("https")) {
final URI uri;
try {
uri = new URI(uriString);
} catch (Exception e) {
throw new SettingsException("Failed to parse HTTPS URI [" + uriString + "]."; e);
}
if (Strings.hasText(uri.getHost()) == false) {
// Example URIs w/o host: "https:/"; "https://"; "https://:443"
throw new SettingsException("Host is missing in HTTPS URI [" + uriString + "].");
}
