# APM Agent data not getting connected/uploaded to APM Server

**URL:** <https://discuss.elastic.co/t/apm-agent-data-not-getting-connected-uploaded-to-apm-server/270319>\
**Category:** APM\
**Tags:** java\
**Created:** [April 16, 2021, 2:41am UTC](https://discuss.elastic.co/t/apm-agent-data-not-getting-connected-uploaded-to-apm-server/270319 "2021-04-16T02:41:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stud21](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@Stud21](https://discuss.elastic.co/u/Stud21)\
**Post date:** [April 16, 2021, 2:41am UTC](https://discuss.elastic.co/t/apm-agent-data-not-getting-connected-uploaded-to-apm-server/270319/1 "2021-04-16T02:41:41Z")

</div>

I unable to setup APM Agent load data to get updated into APM Server.  
In Kibana APM Server status says 'You have correctly setup APM Server'  
However when I click on the Agent status in Kibana it says 'No data has been received from agents yet'.  
However if I go back to APM services, it does show my application listed with Name, Avg. response, Trans. per minute and Error rate %.

I have tried to run the application as stated in Kibana as under:  
sudo java -javaagent:elastic-apm-agent-1.22.0.jar   
-Delastic.apm.service\_name=petclinic-java   
-Delastic.apm.server\_urls=https://xyz.com.au:8200   
-Delastic.apm.secret\_token=   
-Delastic.apm.application\_packages=co.elastic.apm.petclient   
-jar spring-petclinic-2.4.2.jar  
This enables my application and I am able to access, view and use it using a web browser

Looking at the Java application log it shows errors as below:  
'2021-04-16 12:01:08.170 INFO 2892 --- [main] o.s.s.petclinic.PetClinicApplication : Started PetClinicApplication in 12.433 seconds (JVM running for 20.207)  
2021-04-16 12:01:24,168 [elastic-apm-server-reporter] ERROR co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Error trying to connect to APM Server. Some details about SSL configurations corresponding the current connection are logged at INFO level.  
2021-04-16 12:01:24,169 [elastic-apm-server-reporter] INFO co.elastic.apm.agent.report.IntakeV2ReportingEventHandler - Default cipher suites: [TLS\_ECDHE\_ECDSA\_WITH\_AES\_256\_CBC\_SHA384, TLS\_ECDHE\_RSA\_WITH\_AES\_256\_CBC\_SHA384, TLS\_RSA\_WITH\_AES\_256\_CBC\_SHA256, TLS\_ECDH\_ECDSA\_WITH\_AES\_256\_CBC\_SHA384, TLS\_ECDH\_RSA\_WITH\_AES\_256\_CBC\_SHA384, TLS\_DHE\_RSA\_WITH\_AES\_256\_CBC\_SHA256, TLS\_DHE\_DSS\_WITH\_AES\_256\_CBC\_SHA256, TLS\_ECDHE\_ECDSA\_WITH\_AES\_256\_CBC\_SHA, TLS\_ECDHE\_RSA\_WITH\_AES\_256\_CBC\_SHA, TLS\_RSA\_WITH\_AES\_256\_CBC\_SHA, TLS\_ECDH\_ECDSA\_WITH\_AES\_256\_CBC\_SHA, TLS\_ECDH\_RSA\_WITH\_AES\_256\_CBC\_SHA, TLS\_DHE\_RSA\_WITH\_AES\_256\_CBC\_SHA, TLS\_DHE\_DSS\_WITH\_AES\_256\_CBC\_SHA, TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_CBC\_SHA256, TLS\_ECDHE\_RSA\_WITH\_AES\_128\_CBC\_SHA256, TLS\_RSA\_WITH\_AES\_128\_CBC\_SHA256, TLS\_ECDH\_ECDSA\_WITH\_AES\_128\_CBC\_SHA256, TLS\_ECDH\_RSA\_WITH\_AES\_128\_CBC\_SHA256, TLS\_DHE\_RSA\_WITH\_AES\_128\_CBC\_SHA256, TLS\_DHE\_DSS\_WITH\_AES\_128\_CBC\_SHA256, TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_CBC\_SHA, TLS\_ECDHE\_RSA\_WITH\_AES\_128\_CBC\_SHA, TLS\_RSA\_WITH\_AES\_128\_CBC\_SHA, TLS\_ECDH\_ECDSA\_WITH\_AES\_128\_CBC\_SHA, TLS\_ECDH\_RSA\_WITH\_AES\_128\_CBC\_SHA, TLS\_DHE\_RSA\_WITH\_AES\_128\_CBC\_SHA, TLS\_DHE\_DSS\_WITH\_AES\_128\_CBC\_SHA, TLS\_ECDHE\_ECDSA\_WITH\_AES\_256\_GCM\_SHA384, TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_GCM\_SHA256, TLS\_ECDHE\_RSA\_WITH\_AES\_256\_GCM\_SHA384, TLS\_RSA\_WITH\_AES\_256\_GCM\_SHA384, TLS\_ECDH\_ECDSA\_WITH\_AES\_256\_GCM\_SHA384, TLS\_ECDH\_RSA\_WITH\_AES\_256\_GCM\_SHA384, TLS\_DHE\_RSA\_WITH\_AES\_256\_GCM\_SHA384, TLS\_DHE\_DSS\_WITH\_AES\_256\_GCM\_SHA384, TLS\_ECDHE\_RSA\_WITH\_AES\_128\_GCM\_SHA256, TLS\_RSA\_WITH\_AES\_128\_GCM\_SHA256, TLS\_ECDH\_ECDSA\_WITH\_AES\_128\_GCM\_SHA256, TLS\_ECDH\_RSA\_WITH\_AES\_128\_GCM\_SHA256, TLS\_DHE\_RSA\_WITH\_AES\_128\_GCM\_SHA256, TLS\_DHE\_DSS\_WITH\_AES\_128\_GCM\_SHA256, TLS\_EMPTY\_RENEGOTIATION\_INFO\_SCSV]'

Following is the error logged in APM logs:  
'2021-04-15T17:08:17.110+1000 DEBUG [kibana] kibana/connecting\_client.go:74 Trying to obtain connection to Kibana.  
2021-04-15T17:08:17.110+1000 INFO kibana/client.go:119 Kibana url: [https://xyz.com.au:5601](https://xyz.com.au:5601)  
2021-04-15T17:08:17.124+1000 ERROR [kibana] kibana/connecting\_client.go:77 failed to obtain connection to Kibana: fail to get the Kibana version: HTTP GET request to [https://xyz.com.au:5601/api/status](https://xyz.com.au:5601/api/status) fails: . Response: {"statusCode":401,"error":"Unauthorized","message":"Unauthorized"}.  
2021-04-15T17:08:17.282+1000 DEBUG [kibana] kibana/connecting\_client.go:74 Trying to obtain connection to Kibana.'

My query is:  
Do I need to enable SSL connection between APM server and agent? How?  
If APM server status show green and under APM Services the name correctly appears as petclinic-java then what is stopping the data update

---

<div class="post-metadata">

**Author:** ![Sylvain\_Juge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sylvain_juge/32/55521_2.png) [@Sylvain\_Juge](https://discuss.elastic.co/u/Sylvain_Juge)\
**Post date:** [April 19, 2021, 12:59pm UTC](https://discuss.elastic.co/t/apm-agent-data-not-getting-connected-uploaded-to-apm-server/270319/2 "2021-04-19T12:59:44Z")

</div>

Hi @Stud21 ,

There are two things not related here:

1. communication between apm-agent (Java) and apm-server
2. communication between apm-server and Kibana

For (1) you seem to be using an `https` URL, which implies that SSL/TLS is being used to reach to apm-server, if it's a local instance without SSL/TLS enabled you could just try with `http` instead.

For (2) you get an HTTP 401 response code, which means it's not related to SSL/TLS, but more about authorization between apm-server and Kibana.

---

<div class="post-metadata">

**Author:** ![Stud21](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@Stud21](https://discuss.elastic.co/u/Stud21)\
**Post date:** [April 19, 2021, 11:34pm UTC](https://discuss.elastic.co/t/apm-agent-data-not-getting-connected-uploaded-to-apm-server/270319/3 "2021-04-19T23:34:19Z")

</div>

Hi Sylvain,  
I have tried running the java (petclinic) application as under:  
sudo java -javaagent:elastic-apm-agent-1.22.0.jar   
-Delastic.apm.service\_name=petclinic-java   
-Delastic.apm.server\_urls=http://xyz.com.au:8200   
-Delastic.apm.secret\_token=   
-Delastic.apm.application\_packages=co.elastic.apm.petclient   
-jar spring-petclinic-2.4.2.jar

I have verified and find that APM server is working fine with indexes running and APM Server status stating 'You have correctly setup APM Server'.

I have attached the java app output file here.

Conclusion:  
In Kibana, APM agent status still says 'No data has been received from agents yet' and I'm unable to locate any services registered or data in APM

---

<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 10, 2021, 7:35pm UTC](https://discuss.elastic.co/t/apm-agent-data-not-getting-connected-uploaded-to-apm-server/270319/4 "2021-05-10T19:35:09Z")

</div>

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