Curl localhost port 3128: Connection refused

Elastic Stack Elasticsearch
1

Hello everyone!
I am currently using Elasticsearch 5.6.1 and I have the following problem:

curl -X GET http://localhost:9200/
curl: (7) Failed to connect to localhost port 3128: Connection refused

What is this port 3128?

I de-installed and re-installed Elasticsearch several times but it does not help.
I am using Linux Mint Sonya.

Thank you!

2

@Maxclac

Your elasticsearch is pointing to 3128 port. Have you done any modification for port in the elasticsearch.yml file?
share your configuration file

3 
# ======================== Elasticsearch Configuration =========================
#
# NOTE: Elasticsearch comes with reasonable defaults for most settings.
#       Before you set out to tweak and tune the configuration, make sure you
#       understand what are you trying to accomplish and the consequences.
#
# The primary way of configuring a node is via this file. This template lists
# the most important settings you may want to configure for a production cluster.
#
# Please consult the documentation for further information on configuration options:
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
#cluster.name: my-application
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
#node.name: node-1
#
# Add custom attributes to the node:
#
#node.attr.rack: r1
#
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#
#path.data: /path/to/data
#
# Path to log files:
#
#path.logs: /path/to/logs
#
# ----------------------------------- Memory -----------------------------------
#
# Lock the memory on startup:
#
#bootstrap.memory_lock: true
#
# Make sure that the heap size is set to about half the memory available
# on the system and that the owner of the process is allowed to use this
# limit.
#
# Elasticsearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# Set the bind address to a specific IP (IPv4 or IPv6):
#
#network.host: 192.168.0.1
#
# Set a custom port for HTTP:
#
http.port: 9200
#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when new node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
#discovery.zen.ping.unicast.hosts: ["host1", "host2"]
#
# Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):
#
#discovery.zen.minimum_master_nodes: 3
#
# For more information, consult the zen discovery module documentation.
#
# ---------------------------------- Gateway -----------------------------------
#
# Block initial recovery after a full cluster restart until N nodes are started:
#
#gateway.recover_after_nodes: 3
#
# For more information, consult the gateway module documentation.
#
# ---------------------------------- Various -----------------------------------
#
# Require explicit names when deleting indices:
#
#action.destructive_requires_name: true
4

do you use a HTTP proxy at all? you ES seems to be on port 9200 and your are trying to connect to 9200 but curl is trying to go through 3128 so it may be that you have a HTTP proxy configured but not running?

5

I am not sure if I use a HTTP proxy. How would I find out?
I want to work locally, so I guess I should set the hosts to localhost.

6

Only reasonable explanation I can see is that you are using lower case -x

Form curl man page

   -x, --proxy <[protocol://][user:password@]proxyhost[:port]>
          Use the specified proxy.

Try just curl http://localhost:9200/

7

I think I found out the issue.
In my .bashrc file, I left some export http proxy commands from a previous modification.
I removed them now, everything fine.
Thanks!

8

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.