# APM server not connecting to ElasticSearch

**URL:** <https://discuss.elastic.co/t/apm-server-not-connecting-to-elasticsearch/168508>\
**Category:** APM\
**Created:** [February 15, 2019, 3:45am UTC](https://discuss.elastic.co/t/apm-server-not-connecting-to-elasticsearch/168508 "2019-02-15T03:45:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tm8747a](https://avatars.discourse-cdn.com/v4/letter/t/779978/32.png) [@tm8747a](https://discuss.elastic.co/u/tm8747a)\
**Post date:** [February 15, 2019, 3:45am UTC](https://discuss.elastic.co/t/apm-server-not-connecting-to-elasticsearch/168508/1 "2019-02-15T03:45:25Z")

</div>

If you are asking about a problem you are experiencing, please use the following template, as it will help us help you. If you have a different problem, please delete all of this text 🙂

**Kibana version** :  
6.6.0

**Elasticsearch version** :  
6.6.0

**APM Server version** :  
7.0.0-beta1

**APM Agent language and version** :  
none yet

**Browser version** :  
Chrome 72.0.3626.109

**Original install method (e.g. download page, yum, deb, from source, etc.) and version**:  
Zip from dowload page

**Fresh install or upgraded from other version?**  
Fresh install

**Is there anything special in your setup?** For example, are you using the Logstash or Kafka outputs? Are you using a load balancer in front of the APM Servers? Have you changed index pattern, generated custom templates, changed agent configuration etc.  
Running on Windows 10, don't think it's supported but have seen people running it and ElasticSearch and Kibana seem to be working fine

**Description of the problem including expected versus actual behavior. Please include screenshots (if relevant)**:  
After following all the steps to install APM server, when I go to APM in Kibana I see this:

"There's no APM index pattern with the title "apm-\*" available. To use the Query bar, please choose to import the APM index pattern via the Setup Instructions."

When I go to the Setup Instructions, I can see I've done everything mentioned, but when I click Check APM Server Status I get "APM Server has still not connected to Elasticsearch".

When I run apm-server test output command, I get the following output, which seems fine:  
elasticsearch: [http://localhost:9200](http://localhost:9200)...  
parse url... OK  
connection...  
parse host... OK  
dns lookup... OK  
addresses: 127.0.0.1, ::1  
dial up... OK  
TLS... WARN secure connection disabled  
talk to server... OK  
version: 6.6.0

---

<div class="post-metadata">

**Author:** ![tm8747a](https://avatars.discourse-cdn.com/v4/letter/t/779978/32.png) [@tm8747a](https://discuss.elastic.co/u/tm8747a)\
**Post date:** [February 15, 2019, 2:38pm UTC](https://discuss.elastic.co/t/apm-server-not-connecting-to-elasticsearch/168508/2 "2019-02-15T14:38:08Z")

</div>

I guess my assumption that things would work downloading whatever version is on the download page for each component was wrong. I downloaded APM 6.6.0, matching the versions I had for ElasticSearch and Kibana and now I get "You have correctly setup APM Server". So looks like I'm all good there.

---

<div class="post-metadata">

**Author:** ![simitt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simitt/32/106406_2.png) [@simitt](https://discuss.elastic.co/u/simitt)\
**Post date:** [February 15, 2019, 3:51pm UTC](https://discuss.elastic.co/t/apm-server-not-connecting-to-elasticsearch/168508/3 "2019-02-15T15:51:47Z")

</div>

Hi Thomas,  
as you mentioned Kibana 6.6 is not compatible to show APM data ingested with APM Server 7.0.0-beta1.  
Glad to hear everything works now.

---

<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:** [March 8, 2019, 11:59am UTC](https://discuss.elastic.co/t/apm-server-not-connecting-to-elasticsearch/168508/4 "2019-03-08T11:59:39Z")

</div>

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