# APM Node agent won't recognize cloud cert

**URL:** <https://discuss.elastic.co/t/apm-node-agent-wont-recognize-cloud-cert/201677>\
**Category:** APM\
**Tags:** nodejs\
**Created:** [September 30, 2019, 4:12pm UTC](https://discuss.elastic.co/t/apm-node-agent-wont-recognize-cloud-cert/201677 "2019-09-30T16:12:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ftripier\_ionq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ftripier_ionq/32/49396_2.png) [@ftripier\_ionq](https://discuss.elastic.co/u/ftripier_ionq)\
**Post date:** [September 30, 2019, 4:12pm UTC](https://discuss.elastic.co/t/apm-node-agent-wont-recognize-cloud-cert/201677/1 "2019-09-30T16:12:24Z")

</div>

**Kibana version** :  
v7.3.2

**Elasticsearch version** :  
v7.3.2

**APM Server version** :  
v7.3.2

**APM Agent language and version** :  
NodeJS v10.16.3

**Browser version** :

**Original install method (e.g. download page, yum, deb, from source, etc.) and version**:  
npm install/hosted on elastic cloud

**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.

It's a very straightforward set up. We just run a node server on an on-premise ubuntu 16.04 box.

**Description of the problem including expected versus actual behavior. Please include screenshots (if relevant)**:

Basically, our server is failing to talk to APM in any capacity. One-off scripts on the same box and node version work fine.

**Steps to reproduce** :

1. Boot up our server using pm2. Initialize agent.

**Errors in browser console (if relevant)**:

**Provide logs and/or server output (if relevant)**:

Logs of failed event upload:

APM Server transport error (ERR\_TLS\_CERT\_ALTNAME\_INVALID): Hostname/IP does not match certificate's altnames: Host: [2181ff97dfc0444f879ac2b36b34ad67.apm.us-central1.gcp.cloud.es.io](http://2181ff97dfc0444f879ac2b36b34ad67.apm.us-central1.gcp.cloud.es.io). is not in the cert's altnames: DNS:_.gcp.cloud.es.io, DNS:_.apm.europe-west1.gcp.cloud.es.io, DNS:apm.europe-west1.gcp.cloud.es.io, DNS:_.apm.europe-west3.gcp.cloud.es.io, DNS:apm.europe-west3.gcp.cloud.es.io, DNS:_.apm.us-central1.gcp.cloud.es.io, DNS:apm.us-central1.gcp.cloud.es.io, DNS:_.apm.us-west1.gcp.cloud.es.io, DNS:apm.us-west1.gcp.cloud.es.io, DNS:_.us-central1.gcp.cloud.es.io, DNS:us-central1.gcp.cloud.es.io, DNS:_.europe-west1.gcp.cloud.es.io, DNS:europe-west1.gcp.cloud.es.io, DNS:_.europe-west3.gcp.cloud.es.io, DNS:europe-west3.gcp.cloud.es.io, DNS:\*.us-west1.gcp.cloud.es.io, DNS:us-west1.gcp.cloud.es.io, DNS:gcp.cloud.es.io

---

<div class="post-metadata">

**Author:** ![stephenbelanger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenbelanger/32/34880_2.png) [@stephenbelanger](https://discuss.elastic.co/u/stephenbelanger)\
**Post date:** [October 7, 2019, 8:22pm UTC](https://discuss.elastic.co/t/apm-node-agent-wont-recognize-cloud-cert/201677/2 "2019-10-07T20:22:25Z")

</div>

The Node.js agent doesn't currently support custom certs. How are you trying to use it currently?

---

<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:** [October 28, 2019, 4:22pm UTC](https://discuss.elastic.co/t/apm-node-agent-wont-recognize-cloud-cert/201677/3 "2019-10-28T16:22:25Z")

</div>

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