aks browse East US fails connection timed out

[ccit-spence]

error: error upgrading connection: error dialing backend: dial tcp 10.240.0.6:10250: getsockopt: connection timed out

Have tried using Windows and Bash, still the same problem.

AKS Managed

Azure CLI Version: 2.0.30
Kubernetes Version: 1.8.7

[christofferjerrebo]

I'm having the same issue in westeurope.

When getting logs from kubernetes-dashboard I get:

kubectl logs kubernetes-dashboard-546f987686-ptbrr --namespace kube-system
Error from server: Get https://aks-nodepool1-29796037-0:10250/containerLogs/kube-system/kubernetes-dashboard-546f987686-ptbrr/main: dial tcp 10.240.0.5:10250: getsockopt: connection timed out

Azure CLI Version: 2.0.30
Kubernetes client version: v1.10.0
Kubernetes server version: v1.9.6

[sbadakhc]

Seeing timeouts in westeurope also:

kubectl get nodes
Unable to connect to the server: net/http: TLS handshake timeout

[christofferjerrebo]

Same in centralus:

kubectl logs kubernetes-dashboard-69bb965b88-ddgnk --namespace kube-system
Error from server: Get https://aks-nodepool1-35022943-0:10250/containerLogs/kube-system/kubernetes-dashboard-69bb965b88-ddgnk/main: dial tcp 10.240.0.4:10250: getsockopt: connection timed out

[sbadakhc]

This seems to be back up now.

[christofferjerrebo]

I'm still getting getsockopt: connection timed out in both westeurope and centralus.

[trydis]

Timeouts here as well, West Europe.

[thebitguru]

I am a kubernetes learner. What do you get when you run the following commands?

kubectl get pods -n kube-system

kubectl top node

[kahoona77]

I am getting this today as well in West Europe

[snekcz]

The same issue for last few days in West Europe. Most of kubectl exec <pod_name> <command> fails with Error from server: error dialing backend: dial tcp 10.240.0.4:10250: getsockopt: connection timed out. kubectl logs command has the same issue.

Azure CLI version: 2.0.31
Kubectl client version: v1.10.1
Kubernetes cluster version: v1.7.9

[DavidNorena]

+1

[adam-resdiary]

Just for the record, we're seeing the same issue with a kubectl logs command in a cluster in West Europe today:

> kubectl logs grafana-68458768db-zq2c5 --namespace monitoring
Error from server: Get https://aks-nodepool1-28371372-1:10250/containerLogs/monitoring/grafana-68458768db-zq2c5/grafana: dial tcp 10.240.0.5:10250: getsockopt: connection timed out

We're also not able to ssh onto the nodes using the instructions at https://docs.microsoft.com/en-us/azure/aks/aks-ssh because it just hangs when creating the ssh pod without giving us a console.

[adam-resdiary]

Just an update - we managed to sort the problem using the steps Lewis has outlined in #232. It sounds like something had stopped functioning properly on one of our cluster nodes, and restarting the node caused it to start working again.

[sauryadas]

This looks like an old bug and i am going to close it since there has been no activity. Please create a new one if you are still seeing issues

[WiGoy]

I'm having the same issue in East US.
Error from server: error dialing backend: dial tcp 10.240.0.6:10250: i/o timeout

AKS Managed

Azure CLI Version: 2.0.47
Kubernetes Version: 1.12.0

[Khaja514]

I am facing same issue when i am trying to connect my pod using eks kubectl.

$ kubectl exec -it delegate-portal-5f669855f9-82drh bash
Error from server: error dialing backend: dial tcp XXXXXXX:10250: getsockopt: connection refused

$kubectl logs delegate-portal-5f669855f9-82drh
Error from server: Get https://1XXXXXX:10250/containerLogs/default/delegate-portal-5f669855f9-82drh/delegate-portal: dial tcp 1XXXXXX:10250: getsockopt: connection refused

[liambarnett]

@WiGoy @Khaja514 Did you managed to find a solution/workaround for this issue?

[sithumc]

Still getting the issue
error: error upgrading connection: error dialing backend: dial tcp 10.240.0.4:10250: i/o timeout

Restarted cluster and re-scaled cluster but the issue is still there.

Do I need to delete the cluster and re-create? This is production-impaired :(

[jnoller]

Github is not the correct location for production impacting issues or urgent issues. Please open an azure technical support issue so that engineering can examine