# Crashing cluster after kubeadm on VPS

**URL:** <https://discuss.kubernetes.io/t/crashing-cluster-after-kubeadm-on-vps/24478>\
**Category:** General Discussions\
**Tags:** development, network\
**Created:** [June 10, 2023, 7:47pm UTC](https://discuss.kubernetes.io/t/crashing-cluster-after-kubeadm-on-vps/24478 "2023-06-10T19:47:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![basvandriel](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/basvandriel/32/12695_2.png) [@basvandriel](https://discuss.kubernetes.io/u/basvandriel)\
**Post date:** [June 10, 2023, 7:47pm UTC](https://discuss.kubernetes.io/t/crashing-cluster-after-kubeadm-on-vps/24478/1 "2023-06-10T19:47:20Z")

</div>

## Problem

Whenever I create my cluster, and deploy Flannel, it works for maybe ~5 minutes. When I check the cluster info by `kubectl cluster-info`, it shows the correct information. After a while, it simply shows

> The connection to the server \<server\_ip\>:6443 was refused - did you specify the right host or port?

### Cluster information:

Kubernetes version: 1.27.2  
Cloud being used: (put bare-metal if not on a public cloud)  
Installation method: **kubeadm init, directly from the [Installing kubeadm | Kubernetes](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/) page**  
Host OS: **Ubuntu 22.04.2 LTS**  
CNI and version: **Flannel 0.22.0**  
CRI and version: **containerd 1.6.21**

## What I’ve tried

To start off, I followed this tutorial: [https://computingforgeeks.com/deploy-kubernetes-cluster-on-ubuntu-with-kubeadm/](https://computingforgeeks.com/deploy-kubernetes-cluster-on-ubuntu-with-kubeadm/). I didn’t disable the swap, step 3. The CRI part in my containerd config looks like this:

```auto
  [plugins."io.containerd.grpc.v1.cri"]
    stream_server_address = "127.0.0.1"
    stream_server_port = "0"
    systemd_cgroup = true

    [plugins."io.containerd.grpc.v1.cri".cni]
      bin_dir = "/opt/cni/bin"
      conf_dir = "/etc/cni/net.d"
      conf_template = ""
      ip_pref = ""
      max_conf_num = 1

```

When all ready, I initialized my cluster with `sudo kubeadm init --pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=<server_ip>`. This didn’t gave any errors.

## Questions

- What causes this? Is my network configuration off?
- What step am I missing?
- For checking logs, what’s the pod that can cause this? Mostly the kube-proxy one is that gets an error, but see no concrete information other then `dial tcp <serverip>:6443: connect: connection refused` at the end of every statement.