Azure Proxy port or host have been set but proxy type is not defined – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when the Elasticsearch is configured to use Azure as a repository for snapshots, but the proxy type for the Azure connection is not defined, even though the proxy host or port is set. To resolve this issue, you need to specify the proxy type in the Elasticsearch configuration. The proxy type could be either “http” or “https”. If you’re not using a proxy, ensure that the proxy host and port are not set in the configuration.

This guide will help you check for common problems that cause the log ” Azure Proxy port or host have been set but proxy type is not defined. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: azure, repository-azure, repositories.

Log Context

Log “Azure Proxy port or host have been set but proxy type is not defined.” class name is AzureStorageSettings.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 this.timeout = timeout;
 this.maxRetries = maxRetries;
 // Register the proxy if we have any
 // 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.");
 }

 

 [ratemypost]