# Kibana expose with NodePort crash host

**URL:** <https://discuss.elastic.co/t/kibana-expose-with-nodeport-crash-host/358574>\
**Category:** Kibana\
**Tags:** elastic-stack-monitoring\
**Created:** [May 1, 2024, 3:56pm UTC](https://discuss.elastic.co/t/kibana-expose-with-nodeport-crash-host/358574 "2024-05-01T15:56:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MrXY](https://avatars.discourse-cdn.com/v4/letter/m/5f9b8f/32.png) [@MrXY](https://discuss.elastic.co/u/MrXY)\
**Post date:** [May 1, 2024, 3:56pm UTC](https://discuss.elastic.co/t/kibana-expose-with-nodeport-crash-host/358574/1 "2024-05-01T15:56:36Z")

</div>

I am currently trying to set up the ELK stack on my Kubernetes cluster which runs on two VMS. When I try to expose Kibana using type: NodePort my host crashes. However, this only happens with Kibana and I can expose other services without any problems. I use the official Helm Chart. The Website shows for like 0,5sec and afterward the Host System with all the running VMS crash without any logs.  
service:  
type: NodePort  
port: 5601  
nodePort: 31001

I don't want to use an ingress controller because I want to use it locally only.

---

<div class="post-metadata">

**Author:** ![MrXY](https://avatars.discourse-cdn.com/v4/letter/m/5f9b8f/32.png) [@MrXY](https://discuss.elastic.co/u/MrXY)\
**Post date:** [May 2, 2024, 7:04pm UTC](https://discuss.elastic.co/t/kibana-expose-with-nodeport-crash-host/358574/2 "2024-05-02T19:04:23Z")

</div>

I fixed it with an other Host