# tls: first record does not look like a TLS handshake-Status DOWN prometheus/targets

**URL:** <https://forums.percona.com/t/tls-first-record-does-not-look-like-a-tls-handshake-status-down-prometheus-targets/6991>\
**Category:** PMM 1.x\
**Created:** [April 29, 2019, 2:14pm UTC](https://forums.percona.com/t/tls-first-record-does-not-look-like-a-tls-handshake-status-down-prometheus-targets/6991 "2019-04-29T14:14:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tarakdesai](https://avatars.discourse-cdn.com/v4/letter/t/9d8465/32.png) [@tarakdesai](https://forums.percona.com/u/tarakdesai)\
**Post date:** [April 29, 2019, 2:14pm UTC](https://forums.percona.com/t/tls-first-record-does-not-look-like-a-tls-handshake-status-down-prometheus-targets/6991/1 "2019-04-29T14:14:20Z")

</div>

Hello,

PMM server and client are latest version and they are added correctly too as I see this output:

# pmm-admin check-network

PMM Network Status

Server Address | 108.161.xx.xx:8080  
Client Address | 209.236.xx.xx

- System Time  
NTP Server ([0.pool.ntp.org](http://0.pool.ntp.org)) | 2019-04-29 19:30:35 +0000 UTC  
PMM Server | 2019-04-29 19:30:35 +0000 GMT  
PMM Client | 2019-04-29 14:30:35 -0500 CDT  
PMM Server Time Drift | OK  
PMM Client Time Drift | OK  
PMM Client to PMM Server Time Drift | OK

- Connection: Client → Server

* * *

SERVER SERVICE STATUS

* * *

Consul API OK  
Prometheus API OK  
Query Analytics API OK

Connection duration | 2.304325ms  
Request duration | 5.3442ms  
Full round trip | 7.648525ms

- Connection: Client ← Server

* * *

SERVICE TYPE NAME REMOTE ENDPOINT STATUS HTTPS/TLS PASSWORD

* * *

linux:metrics mysql2.lems.in 209.236.xx.xx:42000 DOWN YES -  
mysql:metrics mysql2.lems.in 209.236.xx.xx:42002 DOWN YES -

When an endpoint is down it may indicate that the corresponding service is stopped (run ‘pmm-admin list’ to verify).  
If it’s running, check out the logs /var/log/pmm-\*.log

In logs I see this:

time=“2019-04-29T14:06:53-05:00” level=info msg=“Starting HTTPS server for [https://209.236.113.114:42000/metrics](https://209.236.113.114:42000/metrics) …” source=“server.go:106”  
2019/04/29 14:07:19 http: TLS handshake error from 209.236.xx.xx:57512: tls: first record does not look like a TLS handshake

2019/04/29 14:07:19 http: TLS handshake error from 209.236.xx.xx:55848: tls: first record does not look like a TLS handshake  
2019/04/29 14:10:09 http: TLS handshake error from 103.75.xx.xx:28631: remote error: tls: unknown certificate  
2019/04/29 14:10:09 http: TLS handshake error from 103.75.xx.xx:28630: remote error: tls: unknown certificate  
2019/04/29 14:23:55 http: TLS handshake error from 209.236.xx.xx:55902: tls: first record does not look like a TLS handshake

How can we fix this ?

Thanks