# Critical http://10.54.120.149:9200 seems to be unreachable

**URL:** <https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728>\
**Category:** Kibana\
**Tags:** docker\
**Created:** [May 2, 2025, 5:58am UTC](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728 "2025-05-02T05:58:49Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Madhu\_Challapalli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/madhu_challapalli/32/140968_2.png) [@Madhu\_Challapalli](https://discuss.elastic.co/u/Madhu_Challapalli)\
**Post date:** [May 2, 2025, 5:58am UTC](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728/1 "2025-05-02T05:58:49Z")

</div>

I have used below steps to install and run docker images for Elasticsearch and Kibana.

> **[Start a single-node cluster in Docker | Elastic Docs](https://www.elastic.co/docs/deploy-manage/deploy/self-managed/install-elasticsearch-docker-basic)**
>
> Use Docker commands to start a single-node Elasticsearch cluster for development or testing. You can then run additional Docker commands to add nodes...

 ![elasticsearch4](https://us1.discourse-cdn.com/elastic/original/3X/c/7/c7b0b2910894a99482015f8c5d21c55f637e8f37.jpeg)  
 ![elasticsearch2](https://us1.discourse-cdn.com/elastic/original/3X/2/f/2fbd0f876adad9ef9738b1a42a4e59b72dc5258a.png)  
 ![elasticsearch](https://us1.discourse-cdn.com/elastic/original/3X/c/2/c2fc77964ea5c9bd88bb3b55011cc85fb8f27306.png)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 2, 2025, 6:23am UTC](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728/2 "2025-05-02T06:23:12Z")

</div>



---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [May 2, 2025, 6:42am UTC](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728/3 "2025-05-02T06:42:08Z")

</div>

@Madhu_Challapalli  
Here is The Rest of your post ... as a new user you can not put multiple link in a single post

> We wanted to use Client Connectors such as SQL Server / SharePoint to perform different searches / web crawling / real time indexing and data migration from SQL to Elasticsearch etc.  
> Connectors for Microsoft SQL & SharePoint
> 
> [Self-managed connectors | Elastic Documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/es-build-connector.html)  
> Tried both Self and Elastic managed connectors using Kibana (Failed with authentication from Kibana UI to Local host)
> 
> i tried to run 2nd code to start the container and before run the sync/refresh connector
> 
> it was failing with
> 
> Critical [http://10.54.120.149:9200](http://10.54.120.149:9200/) seems to be unreachable
> 
> any help is greatly appreciated.

Also please do not post pictures of command line / code it is unreadable..... please post formatted text

And elastic starts on `https`

did you follow steps 6,7,8 on the page you linked?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 2, 2025, 6:45am UTC](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728/4 "2025-05-02T06:45:00Z")

</div>



---

<div class="post-metadata">

**Author:** ![Madhu\_Challapalli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/madhu_challapalli/32/140968_2.png) [@Madhu\_Challapalli](https://discuss.elastic.co/u/Madhu_Challapalli)\
**Post date:** [May 2, 2025, 7:57am UTC](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728/5 "2025-05-02T07:57:10Z")

</div>

Thanks Stephen.

Yes i have followed steps 6,7,8. However step 8 is throwing below error.

curl: (60) schannel: CertGetCertificateChain trust error CERT\_TRUST\_REVOCATION\_STATUS\_UNKNOWN  
More details here: [curl - SSL CA Certificates](https://curl.se/docs/sslcerts.html)

curl failed to verify the legitimacy of the server and therefore could not  
establish a secure connection to it. To learn more about this situation and  
how to fix it, please visit the webpage mentioned above.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [May 2, 2025, 4:10pm UTC](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728/6 "2025-05-02T16:10:31Z")

</div>

Your on windows I assume? Windows can be very strict on self signed cerys

Can you try localhost instead of the I

`curl --cacert http_ca.crt -u elastic:$ELASTIC_PASSWORD https://localhost:9200`

Can you exec into the container and try the curl from inside the container... Make sure the point to the full path of the CA cert

---

<div class="post-metadata">

**Author:** ![Madhu\_Challapalli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/madhu_challapalli/32/140968_2.png) [@Madhu\_Challapalli](https://discuss.elastic.co/u/Madhu_Challapalli)\
**Post date:** [May 5, 2025, 5:11am UTC](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728/7 "2025-05-05T05:11:53Z")

</div>

Hi Stephen,  
Can we hop into a call ?  
i can schedule a Zoom call on your convienience.

---

<div class="post-metadata">

**Author:** ![Madhu\_Challapalli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/madhu_challapalli/32/140968_2.png) [@Madhu\_Challapalli](https://discuss.elastic.co/u/Madhu_Challapalli)\
**Post date:** [May 5, 2025, 5:51am UTC](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728/8 "2025-05-05T05:51:11Z")

</div>

Yes i did, Its same error.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [May 5, 2025, 6:22am UTC](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728/9 "2025-05-05T06:22:59Z")

</div>

Hi @Madhu_Challapalli

Apologies, seems like perhaps you're confused a bit.

This is a public forum staffed mostly by by volunteers including people like myself that actually work for elastic but volunteer on the site in our spare time

There are no zoom calls or direct messages to address anyone's topics.

If you'd like help, you're going to have to show the actual commands you ran and the results in text not screenshots.

It's unclear to me how exactly you set up and what state you're in.

We cannot read your images from before.

So if you you want help? You need to show the exact command you ran and the outputs not just say you got an error.

It it's unusual if you're saying you're getting the same error inside the container.

I would suggest starting over with the documentation and step through each step and show us exactly where you're failing.

---

<div class="post-metadata">

**Author:** ![Madhu\_Challapalli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/madhu_challapalli/32/140968_2.png) [@Madhu\_Challapalli](https://discuss.elastic.co/u/Madhu_Challapalli)\
**Post date:** [May 5, 2025, 6:59am UTC](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728/10 "2025-05-05T06:59:29Z")

</div>

Sure Stephen.

i have followed below link to setup Docker compose in my local machine using single node configuration.

> **[Start a single-node cluster in Docker | Elastic Docs](https://www.elastic.co/docs/deploy-manage/deploy/self-managed/install-elasticsearch-docker-basic)**
>
> Use Docker commands to start a single-node Elasticsearch cluster for development or testing. You can then run additional Docker commands to add nodes...

I have completed steps 1 to 7 successfully.

when i tried to run step 8 i.e.  
curl --cacert http\_ca.crt -u elastic:$ELASTIC\_PASSWORD [https://localhost:9200](https://localhost:9200)  
(i have gave full path to my http\_ca.crt)

error i got is  
curl: (60) schannel: CertGetCertificateChain trust error CERT\_TRUST\_REVOCATION\_STATUS\_UNKNOWN  
More details here: [curl - SSL CA Certificates](https://curl.se/docs/sslcerts.html)

curl failed to verify the legitimacy of the server and therefore could not  
establish a secure connection to it. To learn more about this situation and  
how to fix it, please visit the webpage mentioned above.

---

<div class="post-metadata">

**Author:** ![Madhu\_Challapalli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/madhu_challapalli/32/140968_2.png) [@Madhu\_Challapalli](https://discuss.elastic.co/u/Madhu_Challapalli)\
**Post date:** [May 5, 2025, 7:02am UTC](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728/11 "2025-05-05T07:02:15Z")

</div>

i got response from Elastic (Json) with link [https://localhost:9200/](https://localhost:9200/)  
{  
"name" : "**",  
"cluster\_name" : "docker-cluster",  
"cluster\_uuid" : "**",  
"version" : {  
"number" : "9.0.0",  
"build\_flavor" : "default",  
"build\_type" : "docker",  
"build\_hash" : "\*\*",  
"build\_date" : "2025-04-08T15:13:46.049795831Z",  
"build\_snapshot" : false,  
"lucene\_version" : "10.1.0",  
"minimum\_wire\_compatibility\_version" : "8.18.0",  
"minimum\_index\_compatibility\_version" : "8.0.0"  
},  
"tagline" : "You Know, for Search"  
}

but not with [http://localhost:9200/](http://localhost:9200/) (Localhost didnt find)

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [May 5, 2025, 5:01pm UTC](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728/12 "2025-05-05T17:01:39Z")

</div>

> [@Madhu\_Challapalli](#):
>
> error i got is  
> curl: (60) schannel: CertGetCertificateChain trust error CERT\_TRUST\_REVOCATION\_STATUS\_UNKNOWN  
> More details here: [curl - SSL CA Certificates](https://curl.se/docs/sslcerts.html)

That is a windows curl error....

> [@Madhu\_Challapalli](#):
>
> i got response from Elastic (Json) with link [https://localhost:9200/](https://localhost:9200/)

You mean you opened in a browser not clear but that is good....

> [@Madhu\_Challapalli](#):
>
> but not with [http://localhost:9200/](http://localhost:9200/) (Localhost didnt find)

Yes because elastic runs on `https` not on `http`

So I think your elasticsearch is working it is just the windows curl that is not...

So what do you want to do next .... send some data? Use Kibana?

---

<div class="post-metadata">

**Author:** ![Madhu\_Challapalli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/madhu_challapalli/32/140968_2.png) [@Madhu\_Challapalli](https://discuss.elastic.co/u/Madhu_Challapalli)\
**Post date:** [May 6, 2025, 5:48am UTC](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728/13 "2025-05-06T05:48:28Z")

</div>

Yes Stephen when i opened in browser i am able to get json response.

Now i am trying to setup Kibana as per below.  
Run Kibana  
steps 1 to 6 completed.

Configured Kibana also

i am trying to setup a MS SQL connector using Create a connector

[http://localhost:5601/app/elasticsearch/content/connectors](http://localhost:5601/app/elasticsearch/content/connectors)

Choose your deployment method (Run with Docker)  
Create index and generate API key

Run connector service  
Create configuration file  
You need a configuration file with your Elasticsearch and connector details. In your terminal, run the following command to create the config.yml file:

## Run container Run the following command to start the container: Till above completed all steps.

Failing at below step..  
docker run -v "$HOME/elastic-connectors:/config" --tty --rm [docker.elastic.co/integrations/elastic-connectors:9.0.0](http://docker.elastic.co/integrations/elastic-connectors:9.0.0) /app/bin/elastic-ingest -c /config/config.yml

error :-  
[FMWK][05:41:19][ERROR] Cannot connect to host localhost:9200 ssl:default [Connect call failed ('127.0.0.1', 9200)]  
[FMWK][05:41:35][INFO] Waiting for Elasticsearch at [http://localhost:9200](http://localhost:9200) (so far: 31 secs)  
[FMWK][05:41:35][ERROR] Could not connect to the Elasticsearch server  
[FMWK][05:41:35][ERROR] Cannot connect to host localhost:9200 ssl:default [Connect call failed ('127.0.0.1', 9200)]  
[FMWK][05:42:07][INFO] Waiting for Elasticsearch at [http://localhost:9200](http://localhost:9200) (so far: 63 secs)  
[FMWK][05:42:07][ERROR] Could not connect to the Elasticsearch server  
[FMWK][05:42:07][ERROR] Cannot connect to host localhost:9200 ssl:default [Connect call failed ('127.0.0.1', 9200)]  
[FMWK][05:43:11][CRITICAL] [http://localhost:9200](http://localhost:9200) seems to be unreachable. Bye!  
[FMWK][05:43:11][INFO] Bye

error when i changed http to https also in config file same error as below (Run connector service)  
[FMWK][05:44:29][INFO] Waiting for Elasticsearch at [https://localhost:9200](https://localhost:9200) (so far: 1 secs)  
[FMWK][05:44:29][ERROR] Could not connect to the Elasticsearch server  
[FMWK][05:44:29][ERROR] Cannot connect to host localhost:9200 ssl:default [Connect call failed ('127.0.0.1', 9200)]  
[FMWK][05:44:31][INFO] Waiting for Elasticsearch at [https://localhost:9200](https://localhost:9200) (so far: 3 secs)  
[FMWK][05:44:31][ERROR] Could not connect to the Elasticsearch server  
[FMWK][05:44:31][ERROR] Cannot connect to host localhost:9200 ssl:default [Connect call failed ('127.0.0.1', 9200)]  
[FMWK][05:44:35][INFO] Waiting for Elasticsearch at [https://localhost:9200](https://localhost:9200) (so far: 7 secs)  
[FMWK][05:44:35][ERROR] Could not connect to the Elasticsearch server  
[FMWK][05:44:35][ERROR] Cannot connect to host localhost:9200 ssl:default [Connect call failed ('127.0.0.1', 9200)]  
[FMWK][05:44:43][INFO] Waiting for Elasticsearch at [https://localhost:9200](https://localhost:9200) (so far: 15 secs)  
[FMWK][05:44:43][ERROR] Could not connect to the Elasticsearch server  
[FMWK][05:44:43][ERROR] Cannot connect to host localhost:9200 ssl:default [Connect call failed ('127.0.0.1', 9200)]  
[FMWK][05:44:59][INFO] Waiting for Elasticsearch at [https://localhost:9200](https://localhost:9200) (so far: 31 secs)  
[FMWK][05:44:59][ERROR] Could not connect to the Elasticsearch server  
[FMWK][05:44:59][ERROR] Cannot connect to host localhost:9200 ssl:default [Connect call failed ('127.0.0.1', 9200)]

any suggestions pls

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [May 6, 2025, 7:29am UTC](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728/14 "2025-05-06T07:29:15Z")

</div>

Share the connector config file.. especially the elasticsearch section

You will need to set the correct SSL settings

---

<div class="post-metadata">

**Author:** ![Madhu\_Challapalli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/madhu_challapalli/32/140968_2.png) [@Madhu\_Challapalli](https://discuss.elastic.co/u/Madhu_Challapalli)\
**Post date:** [May 6, 2025, 10:15am UTC](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728/15 "2025-05-06T10:15:42Z")

</div>

```auto
content of /usr/share/elasticsearch/config/elasticsearch.yml

=============================================
cluster.name: "docker-cluster"
network.host: 0.0.0.0

#----------------------- BEGIN SECURITY AUTO CONFIGURATION -----------------------
#
# The following settings, TLS certificates, and keys have been automatically      
# generated to configure Elasticsearch security features on 05-05-2025 05:29:58
#
# --------------------------------------------------------------------------------

# Enable security features
xpack.security.enabled: true

xpack.security.enrollment.enabled: true

# Enable encryption for HTTP API client connections, such as Kibana, Logstash, and Agents
xpack.security.http.ssl:
  enabled: true
  keystore.path: certs/http.p12

# Enable encryption and mutual authentication between cluster nodes
xpack.security.transport.ssl:
  enabled: true
  verification_mode: certificate
  keystore.path: certs/transport.p12
  truststore.path: certs/transport.p12
# Create a new cluster with the current node only
# Additional nodes can still join the cluster later
cluster.initial_master_nodes: ["34b60fdf31b2"]

#----------------------- END SECURITY AUTO CONFIGURATION -------------------------

Since my elastic connector is not running due to 
Cannot connect to host localhost:9200 ssl:default [Connect call failed ('127.0.0.1', 9200)]

i dont see the files under elastic connector container as it is not running
docker.elastic.co/integrations/elastic-connectors:9.0.0

Let me know if you need any other files

```

---

<div class="post-metadata">

**Author:** ![Madhu\_Challapalli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/madhu_challapalli/32/140968_2.png) [@Madhu\_Challapalli](https://discuss.elastic.co/u/Madhu_Challapalli)\
**Post date:** [May 6, 2025, 10:59am UTC](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728/16 "2025-05-06T10:59:20Z")

</div>

and below is the file i can see in my local machine but not in container  
C:\Users\*\elastic-connectors\config.yml

## connectors:

connector\_id: "pacTpJYB2tFNEycDT9s8"  
service\_type: "mssql"  
api\_key: "\*\*=="

elasticsearch:  
host: "[https://localhost:9200](https://localhost:9200)"  
api\_key: "\*\*=="

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [May 6, 2025, 3:57pm UTC](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728/17 "2025-05-06T15:57:13Z")

</div>

Your missing all the SSL config in the connector config

Look at the elasticsearch settings

[https://raw.githubusercontent.com/elastic/connectors/main/config.yml.example](https://raw.githubusercontent.com/elastic/connectors/main/config.yml.example)

You need to set and provide the CA

`elasticsearch.ssl: true`

`elasticsearch.ca_certs: /path/to/ca.crt`

or turn off verification (not for production use)

`elasticsearch.verify_certs: false`

---

<div class="post-metadata">

**Author:** ![Madhu\_Challapalli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/madhu_challapalli/32/140968_2.png) [@Madhu\_Challapalli](https://discuss.elastic.co/u/Madhu_Challapalli)\
**Post date:** [May 7, 2025, 6:39am UTC](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728/18 "2025-05-07T06:39:05Z")

</div>

```auto
hi Stephen,

i have ran the below code blocks 

#Create configuration file 
mkdir -p "$HOME/elastic-connectors" && echo "connectors:
-
  connector_id: \"pacTpJYB2tFNEycDT9s8\"
  service_type: \"mssql\"
  api_key: \"cHFjVHBKWUIydEZORXljRFVOc1M6Mm5Ua3NZX1R4bkV1WDI1N2lTOU56Zw==\"
elasticsearch:
  host: \"https://localhost:9200\"
  ssl: false
  verify_certs: false
  ca_certs: \"/usr/share/elasticsearch/config/certs/http_ca.crt\"
  api_key: \"cHFjVHBKWUIydEZORXljRFVOc1M6Mm5Ua3NZX1R4bkV1WDI1N2lTOU56Zw==\"" > "$HOME/elastic-connectors/config.yml"
----------Ran successfully 

#Run the following command to start the container:
docker run \
-v "$HOME/elastic-connectors:/config" \
--tty \
--rm \
docker.elastic.co/integrations/elastic-connectors:9.0.0 \
/app/bin/elastic-ingest \
-c /config/config.yml
-------throwing below error ----------------
[FMWK][06:36:36][INFO] Waiting for Elasticsearch at https://localhost:9200 (so far: 7 secs)
[FMWK][06:36:36][ERROR] Could not connect to the Elasticsearch server
[FMWK][06:36:36][ERROR] Cannot connect to host localhost:9200 ssl:default [Connect call failed ('127.0.0.1', 9200)]
[FMWK][06:36:44][INFO] Waiting for Elasticsearch at https://localhost:9200 (so far: 15 secs)
[FMWK][06:36:44][ERROR] Could not connect to the Elasticsearch server
[FMWK][06:36:44][ERROR] Cannot connect to host localhost:9200 ssl:default [Connect call failed ('127.0.0.1', 9200)]
[FMWK][06:37:00][INFO] Waiting for Elasticsearch at https://localhost:9200 (so far: 31 secs)
[FMWK][06:37:00][ERROR] Could not connect to the Elasticsearch server
[FMWK][06:37:00][ERROR] Cannot connect to host localhost:9200 ssl:default [Connect call failed ('127.0.0.1', 9200)]
[FMWK][06:37:32][INFO] Waiting for Elasticsearch at https://localhost:9200 (so far: 63 secs)
[FMWK][06:37:32][ERROR] Could not connect to the Elasticsearch server
[FMWK][06:37:32][ERROR] Cannot connect to host localhost:9200 ssl:default [Connect call failed ('127.0.0.1', 9200)]

anything i am missing ??`Preformatted text`

```

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [May 7, 2025, 7:27am UTC](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728/19 "2025-05-07T07:27:06Z")

</div>

> [@Madhu\_Challapalli](#):
>
> `ssl: false`

`ssl: true`

Also this is a docker network issue .

When you use `localhost` inside a container that is `localhost` to the container it is not localhost of the server so this will never work

> When working with Docker, "localhost" inside a container does not refer to the host machine's localhost. Instead, it refers to the container's own network interface. To access services running on the host machine from within a Docker container, one can employ several techniques:  
> Using host.docker.internal:  
> This special DNS name resolves to the host machine's internal IP address. It is available on Docker for Mac and Windows and in some Linux environments.

Do a search and learn about this ..

Try

```auto
elasticsearch:
  host: "https://host.docker.internal:9200"

```

---

<div class="post-metadata">

**Author:** ![Madhu\_Challapalli](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/madhu_challapalli/32/140968_2.png) [@Madhu\_Challapalli](https://discuss.elastic.co/u/Madhu_Challapalli)\
**Post date:** [May 7, 2025, 10:14am UTC](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728/20 "2025-05-07T10:14:43Z")

</div>

```auto
Thanks Stephen it worked.
I am able to setup connector.
```

[Next page](https://discuss.elastic.co/t/critical-http-10-54-120-149-9200-seems-to-be-unreachable/377728.md?page=2)
