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

AliYmn · 2017-08-08T06:43:39Z

Hi,

>> kubectl get pods --all-namespaces | grep dashboard
Result ;
The connection to the server localhost:8080 was refused - did you specify the right host or port?

>> kubectl create -f https://git.io/kube-dashboard

Result ; 

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

The text was updated successfully, but these errors were encountered:

xiangpengzhao · 2017-08-08T07:00:06Z

Can you check if your kube-apiserver is running and insecure-port 8080 is enabled?

AliYmn · 2017-08-08T08:40:22Z

@xiangpengzhao No, no employee.

xiangpengzhao · 2017-08-08T08:43:50Z

It should be running. How do you setup your cluster?

AliYmn · 2017-08-08T08:54:30Z

root@ubuntu-512mb-nyc3-01:~$ lsof -i
COMMAND     PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
sshd       1527 root    3u  IPv4  15779      0t0  TCP *:ssh (LISTEN)
sshd       1527 root    4u  IPv6  15788      0t0  TCP *:ssh (LISTEN)
VBoxHeadl 15644 root   22u  IPv4  37266      0t0  TCP localhost:2222 (LISTEN)
sshd      18809 root    3u  IPv4  42637      0t0  TCP 104.131.172.65:ssh->78.187.60.13.dynamic.ttnet.com.tr:63690 (ESTABLISHED)
redis-ser 25193 root    4u  IPv6  56627      0t0  TCP *:6380 (LISTEN)
redis-ser 25193 root    5u  IPv4  56628      0t0  TCP *:6380 (LISTEN)
kubectl   31904 root    3u  IPv4  89722      0t0  TCP localhost:8001 (LISTEN)

xiangpengzhao · 2017-08-08T09:58:34Z

FYI: https://kubernetes.io/docs/setup/pick-right-solution/

xiangpengzhao · 2017-08-09T16:38:11Z

/sig cluster-lifecycle

joshualevy2 · 2017-11-10T18:53:08Z

I had this problem because there was no admin.conf file and I did not have KUBECONFIG=/root/admin.conf set. the admin.conf file is created in /etc/kubernetes by the "kubeadmin init" command and you need to copy it to all your minion nodes. kubeadmin does not do this for you.

gkatsanos · 2017-11-28T15:34:17Z

~/D/p/i/server (master|✔) $ kubectl create -f wtf.yml                                                 16:34:07
W1128 16:34:09.944864   27487 factory_object_mapping.go:423] Failed to download OpenAPI (Get http://localhost:8080/swagger-2.0.0.pb-v1: dial tcp [::1]:8080: getsockopt: connection refused), falling back to swagger
The connection to the server localhost:8080 was refused - did you specify the right host or port?```

```yaml
~/D/p/i/server (master|✔) $ cat wtf.yml                                                               16:34:10
apiVersion: v1
kind: Pod
metadata:
  name: myserver
  labels:
    purpose: demonstrate-envars
spec:
  containers:
  - name: myserver
    image: gkatsanos/server
    env:
    - name: JWT_EXPIRATION_MINUTES
      value: "1140"
    - name: JWT_SECRET
      value: "XXX"
    - name: MONGO_URI
      value: "mongodb://mongodb:27017/isawyou"
    - name: CLIENT_URI
      value: "//localhost:8080/"
    - name: MONGO_URI_TESTS
      value: "mongodb://mongodb:27017/isawyou-test"
    - name: PORT
      value: "3000"

~/D/p/i/server (master|✔) $ kubectl version                                                           16:35:00
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.3", GitCommit:"f0efb3cb883751c5ffdbe6d515f3cb4fbe7b7acd", GitTreeState:"clean", BuildDate:"2017-11-08T18:39:33Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"darwin/amd64"}
The connection to the server localhost:8080 was refused - did you specify the right host or port?

didd · 2018-02-01T09:29:07Z

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. You can read about the "why" here.

MulticsYin · 2018-02-26T00:49:51Z

Maybe you not set environment variables, try this:
export KUBERNETES_MASTER=http://MasterIP:8080
MasterIP was you kubernetes master IP

clenk · 2018-03-02T14:10:00Z

I had this problem because I was running kubectl as the wrong user. I had copied /etc/kubernetes/admin.conf to .kube/config in one user's home directory and needed to run kubectl as that user.

moqichenle · 2018-03-27T17:14:23Z

Run these commands solved this issue:
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

After running them, kubectl is working.

fengerzh · 2018-06-18T08:03:34Z

I don't understand, why this command must be run by normal user but not root user?

Sam-Fireman · 2018-09-11T04:07:03Z

Run these commands solved this issue:
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

After running them, kubectl is working.

prabhakarsultane · 2018-10-11T13:26:17Z

There is a configuration issue, if you have setup kubernetes using root and trying to execute kubectl command from the different user then this error will occur.
To resolved this issue run simply below command
root@devops:~# cp -r .kube/ /home/ubuntu/

root@devops:~# chown -R ubuntu:ubuntu /home/ubuntu/.kube

root@devops:~# su ubuntu

root@devops:~# kubectl get pod -o wide

NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE
cron 1/1 Running 0 2h 10.244.0.97 devops

helloworlde · 2018-10-17T05:01:50Z

Run these commands solved this issue:
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

After running them, kubectl is working.

I tried by this solution on Ubuntu 18.04, but it still not work. At last I found it caused by Swap! So I fixed by disable swap like this:

sudo swapoff -a
sudo chown $(id -u):$(id -g) $HOME/.kube/config

neolit123 · 2018-10-26T23:11:31Z

please try tools like kops or kubeadm that will handle all the setup for you.
they also print instructions in the terminal on how to setup admin.conf or pod-network-plugins.

closing this issue.
for similar questions try stackoverflow:
https://github.com/kubernetes/community/blob/master/contributors/guide/issue-triage.md#user-support-response-example

/close

k8s-ci-robot · 2018-10-26T23:11:32Z

@neolit123: Closing this issue.

In response to this:

please try tools like kops or kubeadm that will handle all the setup for you.
they also print instructions in the terminal on how to setup admin.conf or pod-network-plugins.

closing this issue.
for similar questions try stackoverflow:
https://github.com/kubernetes/community/blob/master/contributors/guide/issue-triage.md#user-support-response-example

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Oyunbold · 2018-11-02T09:26:08Z

kubectl config set-cluster demo-cluster --server=http://localhost:8001

jvleminc · 2019-01-10T14:45:06Z

Run these commands solved this issue:
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

After running them, kubectl is working.

I fixed it through similar commands:
kubernetes-sigs/kubespray#1615 (comment)

HiMyFriend · 2019-04-04T18:40:43Z

mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

Mission complete!

azoaib · 2019-04-16T12:41:55Z

I am using docker-for-mac, got the same issue but restarting docker daemon solved the issue.

soromamadou · 2019-04-19T00:13:38Z

hello,
be sure to not run your command as root. You need to use user account

avaslev · 2019-04-19T21:54:01Z

If after running sudo cp /etc/kubernetes/admin.conf $HOME/ && sudo chown $(id -u):$(id -g) $HOME/admin.conf
Command kubectl config view display like this:

apiVersion: v1
clusters: []
contexts: []
current-context: ""
kind: Config
preferences: {}
users: []

Running this command unset KUBECONFIG solved it.

subeeshvasu · 2019-09-03T12:16:45Z

Run these commands solved this issue:
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

After running them, kubectl is working.

For me kubectl didn't work with the above commands. However, I could make it work after running the following export command in addition to the above commands.
export KUBECONFIG=$HOME/.kube/config

Just to be clear, what worked for me is the following sequence.
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
export KUBECONFIG=$HOME/.kube/config

bogere · 2019-09-04T07:55:14Z

sometimes especially if you on Mac OS, just enable kubernetes on your Docker desktop for Mac.
Ensure that it is running , that is what i did to resolve the above error.

Anuradha677 · 2019-10-03T05:03:21Z

I have found same issue. I ran the below command.
gcloud container clusters get-credentials micro-cluster --zone us-central1-a
The issue is resolved.

p8ul · 2019-10-11T18:26:47Z

I experience this error after switching between projects & login. I solved the issue by running this command

gcloud container clusters get-credentials --region your-region gke-us-east1-01

REF

aescobar-icc · 2019-10-12T02:13:37Z

thanks @p8ul, That solved my issue.

zhangdavids · 2019-11-21T01:09:59Z

Run these commands solved this issue:
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

After running them, kubectl is working.

solved 👏

nightswimmings · 2019-11-25T12:58:43Z

This happened to me because of my .kube/config file having wrong indentations (due to manual editing)

tnduy27 · 2019-12-01T17:47:29Z

I have the same problem and resolved completely. If you are using Ubuntu OS, please follow steps:

remove kubernetes if any: https://stackoverflow.com/questions/44884322/how-to-remove-kubectl-from-ubuntu-16-04-lts
Follow those steps in this: https://ubuntu.com/kubernetes/install

Thanks

manishalankala · 2020-01-28T09:24:00Z

I had this problem because there was no admin.conf file and I did not have KUBECONFIG=/root/admin.conf set. the admin.conf file is created in /etc/kubernetes by the "kubeadmin init" command and you need to copy it to all your minion nodes. kubeadmin does not do this for you.

what was the solution to this??

seyfbarhoumi · 2020-02-05T10:00:32Z

Run these commands solved this issue:
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

After running them, kubectl is working.

Worked for me thanks

ghost · 2020-02-25T19:58:03Z

The connection to the server localhost:8080 was refused - did you specify the right host or port?
This command I have to use in Master or Node because I'm getting error in Node
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

ghost · 2020-03-26T13:40:46Z

cp: cannot stat '/etc/kubernetes/admin.conf': No such file or directory

codebyalokgupta · 2020-05-07T21:51:30Z

If anyone using Docker Desktop on Mac then go to docker desktop preferences and enable Kubernetes. It is not enabled by default. It should show Kubernetes running, after that this should be resolved.

hashimyousaf · 2020-05-17T22:07:06Z

If anyone using Docker Desktop on Mac then go to docker desktop preferences and enable Kubernetes. It is not enabled by default. It should show Kubernetes running, after that this should be resolved.

Thanks, it solved my problem. :)

bng-github · 2020-05-18T14:06:49Z

systemctl status kubelet -> it should be runnning state
kubeadm reset -> reset the kubeadm using this command
Now RUN “kubectl get pods” -> will get the pods

moshinde · 2020-06-19T15:40:55Z

I faced this issue when I installed kubectl with root and initialized kubernetes cluster with different user.
Using the same user resolved this issue

ica10888 · 2020-07-02T05:01:49Z

Maybe there is a reason what caused this:
such like in some container, missing environment variable.
could excute follows command to set the environment variable

export KUBECONFIG=/etc/kubernetes/admin.conf

/etc/kubernetes/admin.conf is volumes on the node master's same path.

felipeschossler · 2020-07-08T03:28:45Z

I had this problem because there was no admin.conf file and I did not have KUBECONFIG=/root/admin.conf set. the admin.conf file is created in /etc/kubernetes by the "kubeadmin init" command and you need to copy it to all your minion nodes. kubeadmin does not do this for you.

I love you, so simple as that! ❤️

ibrahiminui · 2020-07-11T19:22:47Z

If you're using EKS, the error is due to the fact that kubectl isn't working yet. To do this, you need to use the command below

aws eks --region {region} update-kubeconfig --name {}cluster name}

saronavee · 2020-08-09T15:16:45Z

Run these commands solved this issue:
mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

After running them, kubectl is working.

Thank you. it works well 💯

tylerlittlefield · 2020-12-15T19:35:06Z

For anyone who had this working but then it randomly stopped, I noticed that my environment variable was no longer set, below is how I resolved:

# check if env is set
echo $KUBECONFIG

# if it returns nothing, set env
export KUBECONFIG=~/.kube/<name of your config file>

# if you don't have that file to begin with, you might try copying it from master node
scp <user>@<master ip>:~/.kube/config ~/.kube/<name you want to give to config file>

jamesfranklinnetsec · 2020-12-22T07:32:34Z

I had this problem because there was no admin.conf file and I did not have KUBECONFIG=/root/admin.conf set. the admin.conf file is created in /etc/kubernetes by the "kubeadmin init" command and you need to copy it to all your minion nodes. kubeadmin does not do this for you.

thanks this was my problem cheerio

Hawaiideveloper · 2021-04-17T16:39:54Z

Resolved:

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

I suggest clicking the link here

Yavdhesh · 2021-06-23T04:41:38Z

For me I accidently installed kubectl and microk8s both. So, I uninstalled kubectl.
microk8s.kubectl version <---- works fine now

xyzkpz · 2021-07-03T12:25:04Z

if you are getting like this goto this url
https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/
it will fix your errors...
enjoy everyone

preciousonyekwere · 2022-01-02T22:58:55Z

Run these commands solved this issue: mkdir -p $HOME/.kube sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config

After running them, kubectl is working.

run this command as ubuntu user NOT root user if you have issues deploying on k8S

Tebeye · 2022-02-01T17:08:40Z

Hello, I am getting same error even I copied the configuration file from /etc/kubernetes/admin.conf
Even I tried export KUBERNETES_MASTER=http://MasterIP:8080
Does anyone know another alternative to solve this problem?

KalinIvanov-l · 2024-03-29T08:43:53Z

If anyone using Docker Desktop on Mac then go to docker desktop preferences and enable Kubernetes. It is not enabled by default. It should show Kubernetes running, after that this should be resolved.

thanks, solved!

k8s-github-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Aug 8, 2017

k8s-ci-robot added the sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. label Aug 9, 2017

k8s-github-robot removed the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Aug 9, 2017

ghost mentioned this issue Dec 8, 2017

swagger open api error skolodyazhnyy/30-seconds-deployment#1

Open

k8s-ci-robot closed this as completed Oct 26, 2018

xzzh999 mentioned this issue Nov 2, 2018

CentOS 7.2 1151 install AllInOne problem easzlab/kubeasz#354

Closed

sizwe-cry mentioned this issue Jan 2, 2022

dockerfile/ubuntu dockerfile/ubuntu#32

Open

kv5h mentioned this issue Jun 21, 2022

The connection to the server localhost:8080 was refused - did you specify the right host or port? kubernetes/minikube#14363

Closed

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

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

Comments

AliYmn commented Aug 8, 2017

xiangpengzhao commented Aug 8, 2017

AliYmn commented Aug 8, 2017

xiangpengzhao commented Aug 8, 2017

AliYmn commented Aug 8, 2017 • edited

xiangpengzhao commented Aug 8, 2017

xiangpengzhao commented Aug 9, 2017

joshualevy2 commented Nov 10, 2017

gkatsanos commented Nov 28, 2017 • edited

didd commented Feb 1, 2018 • edited

MulticsYin commented Feb 26, 2018

clenk commented Mar 2, 2018

moqichenle commented Mar 27, 2018 • edited

fengerzh commented Jun 18, 2018

Sam-Fireman commented Sep 11, 2018

prabhakarsultane commented Oct 11, 2018 • edited

helloworlde commented Oct 17, 2018

neolit123 commented Oct 26, 2018

k8s-ci-robot commented Oct 26, 2018

Oyunbold commented Nov 2, 2018

jvleminc commented Jan 10, 2019 • edited

HiMyFriend commented Apr 4, 2019

azoaib commented Apr 16, 2019

soromamadou commented Apr 19, 2019

avaslev commented Apr 19, 2019

subeeshvasu commented Sep 3, 2019 • edited

bogere commented Sep 4, 2019

Anuradha677 commented Oct 3, 2019 • edited

p8ul commented Oct 11, 2019 • edited

aescobar-icc commented Oct 12, 2019

zhangdavids commented Nov 21, 2019

nightswimmings commented Nov 25, 2019 • edited

tnduy27 commented Dec 1, 2019

manishalankala commented Jan 28, 2020 • edited

seyfbarhoumi commented Feb 5, 2020

ghost commented Feb 25, 2020

ghost commented Mar 26, 2020

codebyalokgupta commented May 7, 2020

hashimyousaf commented May 17, 2020

bng-github commented May 18, 2020 • edited

moshinde commented Jun 19, 2020

ica10888 commented Jul 2, 2020

felipeschossler commented Jul 8, 2020

ibrahiminui commented Jul 11, 2020

saronavee commented Aug 9, 2020

tylerlittlefield commented Dec 15, 2020

jamesfranklinnetsec commented Dec 22, 2020

Hawaiideveloper commented Apr 17, 2021

Resolved:

Yavdhesh commented Jun 23, 2021

xyzkpz commented Jul 3, 2021 • edited

preciousonyekwere commented Jan 2, 2022

Tebeye commented Feb 1, 2022

KalinIvanov-l commented Mar 29, 2024

AliYmn commented Aug 8, 2017 •

edited

gkatsanos commented Nov 28, 2017 •

edited

didd commented Feb 1, 2018 •

edited

moqichenle commented Mar 27, 2018 •

edited

prabhakarsultane commented Oct 11, 2018 •

edited

jvleminc commented Jan 10, 2019 •

edited

subeeshvasu commented Sep 3, 2019 •

edited

Anuradha677 commented Oct 3, 2019 •

edited

p8ul commented Oct 11, 2019 •

edited

nightswimmings commented Nov 25, 2019 •

edited

manishalankala commented Jan 28, 2020 •

edited

bng-github commented May 18, 2020 •

edited

xyzkpz commented Jul 3, 2021 •

edited