# Crashing the Kubernetes cluster **URL:** \ **Category:** General Discussions\ **Tags:** apiserver\ **Created:** [October 13, 2024, 8:26am UTC](https://discuss.kubernetes.io/t/crashing-the-kubernetes-cluster/30104 "2024-10-13T08:26:42Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Navid\_Talesh](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/navid_talesh/32/15998_2.png) [@Navid\_Talesh](https://discuss.kubernetes.io/u/Navid_Talesh)\ **Post date:** [October 13, 2024, 8:26am UTC](https://discuss.kubernetes.io/t/crashing-the-kubernetes-cluster/30104/1 "2024-10-13T08:26:42Z")
hello One of our colleagues started to destroy the Kubernetes cluster when he was fired. So now when I run every command from Kubernetes, I can’t see anything. I hit the command kubectl cluster-info dump I get a same error The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?. I hit the command kubectl get po -v=10 I get a bunch of errors Please help me. Thank you I1013 11:53:33.096288 6149 round\_trippers.go:553] GET [https://127.0.0.1:6443/api?timeout=32s](https://127.0.0.1:6443/api?timeout=32s) in 0 milliseconds I1013 11:53:33.096590 6149 round\_trippers.go:570] HTTP Statistics: DNSLookup 0 ms Dial 0 ms TLSHandshake 0 ms Duration 0 ms I1013 11:53:33.096669 6149 round\_trippers.go:577] Response Headers: E1013 11:53:33.097124 6149 memcache.go:265] couldn’t get current server API group list: Get “[https://127.0.0.1:6443/api?timeout=32s](https://127.0.0.1:6443/api?timeout=32s)”: dial tcp 127.0.0.1:6443: connect: connection refused I1013 11:53:33.097221 6149 cached\_discovery.go:120] skipped caching discovery info due to Get “[https://127.0.0.1:6443/api?timeout=32s](https://127.0.0.1:6443/api?timeout=32s)”: dial tcp 127.0.0.1:6443: connect: connection refused I1013 11:53:33.097570 6149 helpers.go:264] Connection error: Get [https://127.0.0.1:6443/api?timeout=32s:](https://127.0.0.1:6443/api?timeout=32s:) dial tcp 127.0.0.1:6443: connect: connection refused The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?