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

Average Read Time

2 Mins

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 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. To understand the issues related to this log, read the explanation below about the following 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 to analyze Elasticsearch configuration and help resolve this error.

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 {

 

Watch a demo of the Check-Up:

Analyze your cluster