Elasticsearch error: This is not an HTTP port
Written By
Gustavo Vasconcelos
How To articles are not official guidelines or officially
supporteddocumentation. They are community-contributed content and may
not alwaysreflect the latest updates to Liferay DXP. We welcome your
feedback toimprove How to articles!
While we make every effort to ensure this Knowledge Base is accurate,
itmay not always reflect the most recent updates or official
guidelines.We appreciate your understanding and encourage you to reach
out with anyfeedback or concerns.
Legacy Article
You are viewing an article from our legacy
"FastTrack"publication program, made available for
informational purposes. Articlesin this program were published without a
requirement for independentediting or verification and are provided
"as is" withoutguarantee.
Before using any information from this article, independently verify
itssuitability for your situation and project.
Issue
- When configuring a remote Elasticsearch server the Search > Connections screen shows the error java.lang.RuntimeException: error while performing request.
- The logs show the message: Not a valid protocol version: This is not an HTTP port.
Environment
- Any DXP
- Any Elasticsearch running in Remote mode
Resolution
- Elastic search has two main ports for communication: 9200 and 9300 (by default);
- This error rises if you configured the transport port (9300) as a request port (9200);
- Configure the Network Host Addresses parameter with the search server hostname and the correct request port (9200 in most cases), ex: search:9200
Did this article resolve your issue ?