Proxy port must be between 1 and 65534; but was – Elasticsearch Error How To Solve Related Issues



Proxy port must be between 1 and 65534; but was – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch 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 causing 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. 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: plugin.


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 discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

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 = 65535) {
  throw new ElasticsearchParseException("Proxy port must be between 1 and 65534; but was " + port);
  }
  }
  }
 
  if (port == null || host == null) {

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Python server "Only one usage of each socket address is normally permitted" -views 62,485 ,score 23

Elastic/elasticsearch-docker not assigning permissions to data …  



Find Configuration Errors

Analyze Now