# Monitoring error after enabling security
**URL:** https://discuss.elastic.co/t/monitoring-error-after-enabling-security/171395
**Category:** Kibana
**Tags:** elastic-stack-security
**Created:** [March 7, 2019, 11:05pm UTC](https://discuss.elastic.co/t/monitoring-error-after-enabling-security/171395 "2019-03-07T23:05:41Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@rugenl](https://discuss.elastic.co/u/rugenl)
#### Post date: [March 7, 2019, 11:05pm UTC](https://discuss.elastic.co/t/monitoring-error-after-enabling-security/171395/1 "2019-03-07T23:05:41Z")
We are trying to learn how to setup security. We have TLS for the transport using certutil, we have TSL for http using a commercial cert, setup default account passwords and connected via Kibana using the elastic account. What we have tried in Kibana works except for Monitoring, it gets a popup error box
> Monitoring Request Error
>
> No Living connections: Check the Elasticsearch Monitoring cluster network connection and refer to the Kibana logs for more information.
>
> HTTP 503
This may be related from kibana log, but there are 1000's of lines:
> {"type":"error","@timestamp":"2019-03-07T23:03:09Z","tags":["error","monitoring-ui"],"pid":205462,"level":"error","error":{"message":"No Living connections","name":"Error","stack":"Error: No Living connections\n at sendReqWithConnection (/usr/share/kibana/node\_modules/elasticsearch/src/lib/transport.js:226:15)\n at next (/usr/share/kibana/node\_modules/elasticsearch/src/lib/connection\_pool.js:214:7)\n at process.\_tickCallback (internal/process/next\_tick.js:61:11)"},"message":"No Living connections"}
> {"type":"log","@timestamp":"2019-03-07T23:03:09Z","tags":["warning","elasticsearch","monitoring-ui"],"pid":205462,"message":"Unable t
> o revive connection: [https://localhost:9200/](https://localhost:9200/)"}
> {"type":"log","@timestamp":"2019-03-07T23:03:09Z","tags":["warning","elasticsearch","monitoring-ui"],"pid":205462,"message":"No livin
> g connections"}
> {"type":"error","@timestamp":"2019-03-07T23:03:09Z","tags":["error","monitoring-ui"],"pid":205462,"level":"error","error":{"message":
> "No Living connections","name":"Error","stack":"Error: No Living connections\n at sendReqWithConnection (/usr/share/kibana/node\_mo
> dules/elasticsearch/src/lib/transport.js:226:15)\n at next (/usr/share/kibana/node\_modules/elasticsearch/src/lib/connection\_pool.j
> s:214:7)\n at process.\_tickCallback (internal/process/next\_tick.js:61:11)"},"message":"No Living connections"}
> {"type":"response","@timestamp":"2019-03-07T23:03:09Z","tags":,"pid":205462,"method":"post","statusCode":503,"req":{"url":"/api/monitoring/v1/clusters","method":"post","headers":{"host":"met-elk-exp6a.missouri.edu:5601","connection":"keep-alive","content-length":"81","accept":"application/json, text/plain, _/_","origin":"[http://met-elk-exp6a.missouri.edu:5601](http://met-elk-exp6a.missouri.edu:5601)","kbn-version":"6.6.1","user-agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36","content-type":"application/json;charset=UTF-8","referer":"[http://met-elk-exp6a.missouri.edu:5601/app/monitoring","accept-encoding":"gzip](http://met-elk-exp6a.missouri.edu:5601/app/monitoring%22,%22accept-encoding%22:%22gzip), deflate","accept-language":"en-US,en;q=0.9"},"remoteAddress":"161.130.254.132","userAgent":"161.130.254.132","referer":"[http://met-elk-exp6a.missouri.edu:5601/app/monitoring"},"res":{"statusCode":503,"responseTime":117,"contentLength":9},"message":"POST](http://met-elk-exp6a.missouri.edu:5601/app/monitoring%22%7D,%22res%22:%7B%22statusCode%22:503,%22responseTime%22:117,%22contentLength%22:9%7D,%22message%22:%22POST) /api/monitoring/v1/clusters 503 117ms - 9.0B"}
---
### Author:  [@rugenl](https://discuss.elastic.co/u/rugenl)
#### Post date: [March 8, 2019, 2:24pm UTC](https://discuss.elastic.co/t/monitoring-error-after-enabling-security/171395/2 "2019-03-08T14:24:33Z")
I think it's a certificate trust failure on [https://localhost:9200](https://localhost:9200)
---
### Author:  [@rashmi](https://discuss.elastic.co/u/rashmi)
#### Post date: [March 8, 2019, 4:12pm UTC](https://discuss.elastic.co/t/monitoring-error-after-enabling-security/171395/3 "2019-03-08T16:12:52Z")
HI
Are you using a remote monitoring cluster ? if not, the ssl settings you specify for the primary Elasticsearch connection should be sufficient.
Let us know and we can help you further ,
Thanks
Rashmi
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 5, 2019, 4:14pm UTC](https://discuss.elastic.co/t/monitoring-error-after-enabling-security/171395/5 "2019-04-05T16:14:53Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.