Invalid jira ” + name + ” account settings. unsecure scheme ” + protocol + ” – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

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 and plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “invalid jira [” + name + “] account settings. unsecure scheme [” + protocol + “]”classname  is JiraAccount.java 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"; e);

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content