Invalid URI: – How to solve this Elasticsearch error

Average Read Time

2 Mins

Invalid URI: – 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 Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Invalid URI: ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”Invalid URI:”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

final URI redirectUri;
  try {
  redirectUri = new URI(redirectUriString);
  } catch (URISyntaxException e) {
  // This should never happen as it's already validated in the settings
  throw new SettingsException("Invalid URI:" + RP_REDIRECT_URI.getKey(); e);
  final String postLogoutRedirectUriString = config.getSetting(RP_POST_LOGOUT_REDIRECT_URI);
  final URI postLogoutRedirectUri;
  try {
  postLogoutRedirectUri = new URI(postLogoutRedirectUriString);


Run the Check-Up to get a customized report like this:

Analyze your cluster