Why does Helm time out on almost every action?

I'm trying to set up helm for the first time and I'm having troubles.

First, I've created account with cluster-admin role. (According to https://github.com/kubernetes/helm/blob/master/docs/rbac.md#example-service-account-with-cluster-admin-role ).

After that I've initialized brand new helm tiller by using helm init --service-account=tiller and it was successful.

Now when I'm trying to install something:

• First try:

  $ helm repo add gitlab https://charts.gitlab.io$ helm install --name gitlab-runner -f gitlab-runner-values.yaml gitlab/gitlab-runner

  where gitlab-runner-values.yaml looks like this:

  gitlabUrl: https://my-gitlab.domain.comrunnerRegistrationToken: "MY_GITLAB_RUNNER_TOKEN"concurrent: 10

• Second try (as I was not sure if there is an issue with custom repo, so I tried from official):

  $ helm install stable/kibana

I'm getting this error:

Error: forwarding ports: error upgrading connection: error dialing backend: dial tcp 192.168.0.18:10250: getsockopt: connection timed out

I noticed that 192.168.0.18 is visble on pod list:

kube-system   kube-proxy-kzflh                        1/1       Running   0          7d        192.168.0.18   kube-worker-7kube-system   weave-net-jq4n4                         2/2       Running   2          7d        192.168.0.18   kube-worker-7

and that tiller is running on the same node:

kube-system   tiller-deploy-5b48764ff7-qtv9v          1/1       Running   0          3m        10.38.0.1      kube-worker-7

I was told that I probably don't have permission to pods/port-forward and list pods, but kubectl auth can-i create pods/portforward tells me that I can do this (the same with list pods)

Also helm list is throwing the same error as install.