The connection to the server localhost:8080 was refused - did you specify the right host or port?

[twel...@noon.com]

I'm following the kubernetes getting started guide for the first time:

https://kubernetes.io/docs/getting-started-guides/gce/#starting-a-cluster

However, when I get to the step:

kubectl get --all-namespaces services

I get this error:

---
root@control:~# kubectl get --all-namespaces services
The connection to the server localhost:8080 was refused - did you specify the right host or port?
---

It doesn't look like a service was to be set up to run at any point on port 8080.
Why am I getting this error and how can I fix it?

Thanks in advance,
Traiano

[secmask]

I got the same trouble since nearly release, seem must use KUBECONFIG explicit

  sudo cp /etc/kubernetes/admin.conf $HOME/
  sudo chown $(id -u):$(id -g) $HOME/admin.conf
  export KUBECONFIG=$HOME/admin.conf

[Ahmet Alp Balkan]

Could you contribute back to the https://github.com/kubernetes/kubernetes.github.io repository please if you figured out the solution?

--
You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

[sarah....@crunchydata.com]

I'm having this same issue and haven't been able to come to a workaround yet. Have you managed to figure anything out?

[nali...@gmail.com]

On Monday, May 15, 2017 at 1:06:25 PM UTC+5:30, secmask wrote:
> I got the same trouble since nearly release, seem must use KUBECONFIG explicit
>

> I also have same issue. please tell me if you figured it out. this is getting some times only. cant even access dashboard or anythings

[nali...@gmail.com]

On Monday, May 15, 2017 at 1:06:25 PM UTC+5:30, secmask wrote:

I think my problem is api-server restarting always. don't have idea why this is happening

[AJ NOURI]

Solved by getting credentials for the cluster:

> gcloud container clusters get-credentials <cluster-name> --zone us-east1-d --project <project-name>

[rollr...@gmail.com]

I'm facing the same issue on worker node, and this is on premises cluster setup not on google cloud.

Do we need to setup weave-net on worker nodes as well?

[chellar...@gmail.com]

On Wednesday, 17 January 2018 10:20:26 UTC+5:30, rollr...@gmail.com wrote:
> I'm facing the same issue on worker node, and this is on premises cluster setup not on google cloud.
>
> Do we need to setup weave-net on worker nodes as well?

On my case this is happening due to a failing kubelet service('service kubelet status') and I had to do 'swapoff -a' to disable paging and swapping which fixed the problem

#swapoff -a

[Sunil Bhai]

I have posted solutions and references on the below link. Kindly check

https://waterplacid.com/k8-docker/