Issue in Optscale server

[surendra-ta]

Hello team @ek-hystax @tm-hystax @antoniodimariano ,

I have hosted my Optscale server on an AWS EC2 instance. Yesterday, everything was working fine, but today, when I open the URL, it shows "Site can't be reached." My AWS instance is running fine. However, when I open the EC2 terminal and check the nodes using the command:

kubectl get nodes

I receive the following error:

The connection to the server 172.XX.10.XXX:6443 was refused - did you specify the right host or port?

Please guide me on how to troubleshoot this issue.

[DimaRyn]

Hello.
Please show the output of the command below
service kubelet status
Also please clarify if you have tried rebooting the instance

[DimaRyn]

Also, please see the docker status:
service docker status
if you find that it is not running then please restart it

[surendra-ta]

No, I didn’t make any changes. The site automatically started showing "Site can't be reached," and I noticed that Kubelet was inactive. I started the Kubelet service, but it becomes inactive every hour, requiring me to manually restart it for the OptScale server to run. I'm facing this recurring issue and need to restart Kubelet every hour.