Proxy port must be between 1 and 65534 but was – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when the proxy port number configured in Elasticsearch is not within the valid range of 1 to 65534. The port number is either less than 1 or greater than 65534. To resolve this issue, you should check your Elasticsearch configuration file and ensure that the proxy port number is within the valid range. If it’s not, adjust it accordingly. Also, make sure that the chosen port is not being used by another service to avoid conflicts.

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.

Log Context

Log “Proxy port must be between 1 and 65534; but was” class name 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) {

 

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?