Proxy port must be between 1 and 65534; but was – 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 ” Proxy port must be between 1 and 65534; but was ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: 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 “Proxy port must be between 1 and 65534; but was”classname  is HttpProxy.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} else if (SCHEME.match(currentFieldName; parser.getDeprecationHandler())) {
 scheme = Scheme.parse(parser.text());
 } else if (PORT.match(currentFieldName; parser.getDeprecationHandler())) {
 port = parser.intValue();
 if (port <= 0 || port >= 65535) {
 throw new ElasticsearchParseException("Proxy port must be between 1 and 65534; but was " + port);
 }
 }
 } 
 if (port == null || host == null) {

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content