Azure Proxy type has been set but proxy host or port is not defined. – How to solve this Elasticsearch error

Azure Proxy type has been set but proxy host or port is not defined. – 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 ” Azure Proxy type has been set but proxy host or port is not defined. ” 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: repositories, azure, repository-azure and plugins.

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”Azure Proxy type has been set but proxy host or port is not defined.”classname  is AzureStorageSettings.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

// Validate proxy settings
  if (proxyType.equals(Proxy.Type.DIRECT) && ((proxyPort != 0) || Strings.hasText(proxyHost))) {
  throw new SettingsException("Azure Proxy port or host have been set but proxy type is not defined.");
  }
  if ((proxyType.equals(Proxy.Type.DIRECT) == false) && ((proxyPort == 0) || Strings.isEmpty(proxyHost))) {
  throw new SettingsException("Azure Proxy type has been set but proxy host or port is not defined.");
  }
 
  if (proxyType.equals(Proxy.Type.DIRECT)) {
  proxy = null;
  } else {

 

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

Analyze your cluster