# Metricbeat in Kubernetes - 404 error for Kubernetes module events

**URL:** <https://discuss.elastic.co/t/metricbeat-in-kubernetes-404-error-for-kubernetes-module-events/181653>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [May 17, 2019, 8:37pm UTC](https://discuss.elastic.co/t/metricbeat-in-kubernetes-404-error-for-kubernetes-module-events/181653 "2019-05-17T20:37:31Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![chandra2037](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chandra2037/32/72142_2.png) [@chandra2037](https://discuss.elastic.co/u/chandra2037)\
**Post date:** [June 3, 2019, 4:17pm UTC](https://discuss.elastic.co/t/metricbeat-in-kubernetes-404-error-for-kubernetes-module-events/181653/4 "2019-06-03T16:17:59Z")

</div>

Finally able to get it working.  
Followed the instructions given by this [post](https://discuss.elastic.co/t/metricbeat-not-reporting-on-port-10255-anymore-using-latest-kubernetes-how-to-use-the-secured-port-10250/153605/4)  
Where configured hosts as `https://${NODE_NAME}:10250`, then also I was getting “`x509: certificate signed by unknown authority`” error. As per this [post](https://discuss.elastic.co/t/kubernetes-module-kubelet-ssl/147770/10) disabled SSL verification for now, then able to get the Kubernetes metrics.

---

_[View the full topic](https://discuss.elastic.co/t/metricbeat-in-kubernetes-404-error-for-kubernetes-module-events/181653)._