# ElasticSearch with mongo

**URL:** <https://discuss.elastic.co/t/elasticsearch-with-mongo/237838>\
**Category:** Elasticsearch\
**Created:** [June 19, 2020, 4:43pm UTC](https://discuss.elastic.co/t/elasticsearch-with-mongo/237838 "2020-06-19T16:43:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rodrigo\_Ceballos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rodrigo_ceballos/32/46306_2.png) [@Rodrigo\_Ceballos](https://discuss.elastic.co/u/Rodrigo_Ceballos)\
**Post date:** [June 19, 2020, 4:43pm UTC](https://discuss.elastic.co/t/elasticsearch-with-mongo/237838/1 "2020-06-19T16:43:51Z")

</div>

Hi.

I hope you can help me or that someone has the experience already passed.

It happens that I want to start working my mongo data in elastic, so I'm doing a process that synchronizes mongo with elastic, For that I am using transporter, which I have installed it and I already created the transport named pipeline.js which has the following configuration:

"var source = mongodb({  
"uri": "mongodb://user:password@IP:27017/prueba"  
})  
var sink = elasticsearch({  
"uri": "IP:9200/test"  
})

t.Source("source", source, "/._/").Save("sink", sink, "/._/")"

I Run **./transporter-0.5.2-linux-amd64 run pipeline.js** and the following error appears:

"panic: connection error, http:// [recovered]  
panic: Panic at 32: connection error, http:// [recovered]  
panic: Panic at 32: connection error, http://"

I have mongo and elestic on different machines, but on the same network.

I have elastic with security disabled (xpack.security.enabled: false)

Thank you. Regards!

Rodrigo

---

<div class="post-metadata">

**Author:** ![Vinayak\_Sapre](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vinayak_sapre/32/45939_2.png) [@Vinayak\_Sapre](https://discuss.elastic.co/u/Vinayak_Sapre)\
**Post date:** [June 20, 2020, 4:32am UTC](https://discuss.elastic.co/t/elasticsearch-with-mongo/237838/2 "2020-06-20T04:32:51Z")

</div>

Hi Rodrigo,

1. Check if ES is accessible from the host running transporter.  
`curl http://<ElasticSearch Node IP>:9200`

2. Try changing elasticsearch uri in sink to include protocol. http://:9200/test.

---

<div class="post-metadata">

**Author:** ![Rodrigo\_Ceballos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rodrigo_ceballos/32/46306_2.png) [@Rodrigo\_Ceballos](https://discuss.elastic.co/u/Rodrigo_Ceballos)\
**Post date:** [June 21, 2020, 2:15am UTC](https://discuss.elastic.co/t/elasticsearch-with-mongo/237838/3 "2020-06-21T02:15:07Z")

</div>

Hi.

Thanks for your answer. I answer below:

1.- Check if ES is accessible from the host running transporter.  
`curl http://<ElasticSearch Node IP>:9200`

answer; If I arrive. Respons the following.

"{  
"name" : "Host.localdomain",  
"cluster\_name" : "test",  
"cluster\_uuid" : "BxO2hjTlRw-u-8fKJui\_DQ",  
"version" : {  
"number" : "7.7.0",  
"build\_flavor" : "default",  
"build\_type" : "rpm",  
"build\_hash" : "81a1e9eda8e6183f5237786246f6dced26a10eaf",  
"build\_date" : "2020-05-12T02:01:37.602180Z",  
"build\_snapshot" : false,  
"lucene\_version" : "8.5.1",  
"minimum\_wire\_compatibility\_version" : "6.8.0",  
"minimum\_index\_compatibility\_version" : "6.0.0-beta1"  
},  
"tagline" : "You Know, for Search"  
"  
2.- Try changing elasticsearch uri in sink to include protocol. http://:9200/test.

answer; I included http protocol in Sink, but I have the same problem. It does not fix the error.

If you have any other information about what may be causing the problem, I would appreciate it.

At the same time I am evaluating some other way to synchronize

Greetings and thanks

Rodrigo

---

<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:** [July 19, 2020, 2:15am UTC](https://discuss.elastic.co/t/elasticsearch-with-mongo/237838/4 "2020-07-19T02:15:13Z")

</div>

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