Invalid jira name account settings unsecure scheme protocol – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when the Jira account settings in Elasticsearch are invalid, specifically due to an unsecure scheme or protocol. This could be because the protocol being used is not secure (like HTTP instead of HTTPS). To resolve this issue, you can: 1) Check and correct the Jira account settings in Elasticsearch, ensuring that all details are accurate. 2) Switch to a secure protocol such as HTTPS. 3) If the protocol cannot be changed, consider implementing additional security measures like VPNs or firewalls to secure the connection.

This guide will help you check for common problems that cause the log ” invalid jira [” + name + “] account settings. unsecure scheme [” + protocol + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: settings, plugin.

Log Context

Log “invalid jira [” + name + “] account settings. unsecure scheme [” + protocol + “]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (uri.getScheme() == null) {
 throw new URISyntaxException("null"; "No scheme defined in url");
 Scheme protocol = Scheme.parse(uri.getScheme());
 if ((protocol == Scheme.HTTP) && (Booleans.isTrue(settings.get(ALLOW_HTTP_SETTING)) == false)) {
 throw new SettingsException("invalid jira [" + name + "] account settings. unsecure scheme [" + protocol + "]");
 this.url = uri;
 } catch (URISyntaxException | IllegalArgumentException e) {
 throw new SettingsException(
 "invalid jira [" + name + "] account settings. invalid [" + SECURE_URL_SETTING.getKey() + "] setting";