# After reboot of the system not getting any response for kubectl commands

**URL:** <https://discuss.kubernetes.io/t/after-reboot-of-the-system-not-getting-any-response-for-kubectl-commands/23022>\
**Category:** microk8s\
**Created:** [February 10, 2023, 4:04am UTC](https://discuss.kubernetes.io/t/after-reboot-of-the-system-not-getting-any-response-for-kubectl-commands/23022 "2023-02-10T04:04:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![soumik\_ghosh](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/soumik_ghosh/32/11797_2.png) [@soumik\_ghosh](https://discuss.kubernetes.io/u/soumik_ghosh)\
**Post date:** [February 10, 2023, 4:04am UTC](https://discuss.kubernetes.io/t/after-reboot-of-the-system-not-getting-any-response-for-kubectl-commands/23022/1 "2023-02-10T04:04:31Z")

</div>

sudo microk8s kubectl get nodes  
error: Get “[https://127.0.0.1:16443/api?timeout=32s](https://127.0.0.1:16443/api?timeout=32s)”: net/http: TLS handshake timeout - error from a previous attempt: read tcp 127.0.0.1:36260-\>127.0.0.1:16443: read: connection reset by peer

---

<div class="post-metadata">

**Author:** ![gsaiprasanna](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/gsaiprasanna/32/12593_2.png) [@gsaiprasanna](https://discuss.kubernetes.io/u/gsaiprasanna)\
**Post date:** [May 24, 2023, 12:00am UTC](https://discuss.kubernetes.io/t/after-reboot-of-the-system-not-getting-any-response-for-kubectl-commands/23022/2 "2023-05-24T00:00:24Z")

</div>

did you find the solution for this?