Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to enable dashboard: dial tcp 127.0.0.1:22: connect: connection refused #3971

Closed
GiovanniColonni opened this issue Mar 26, 2019 · 3 comments
Labels
co/dashboard dashboard related issues help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/backlog Higher priority than priority/awaiting-more-evidence. r/2019q2 Issue was last reviewed 2019q2

Comments

@GiovanniColonni
Copy link

GiovanniColonni commented Mar 26, 2019

i use : minikube dashboard (with root permission)

the output of command :
Unable to enable dashboard: [command runner: getting ssh client for bootstrapper: Error dialing tcp via ssh client: dial tcp 127.0.0.1:22: connect: connection refused]

SO= ubuntu 18.04
i don't know how to solve it, thanks

@balopat balopat added the co/dashboard dashboard related issues label Apr 4, 2019
@balopat
Copy link
Contributor

balopat commented Apr 4, 2019

can you please confirm what driver are you using? Is it --vm-driver=none?

@balopat balopat added the triage/needs-information Indicates an issue needs more information in order to work on it. label Apr 4, 2019
@tstromberg tstromberg added the priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. label Apr 5, 2019
@tstromberg tstromberg changed the title Unable to enable dashboard getting ssh client for bootstrapper Unable to enable dashboard: ssh client: dial tcp 127.0.0.1:22: connect: connection refused Apr 5, 2019
@tstromberg tstromberg changed the title Unable to enable dashboard: ssh client: dial tcp 127.0.0.1:22: connect: connection refused Unable to enable dashboard: dial tcp 127.0.0.1:22: connect: connection refused Apr 5, 2019
@tstromberg
Copy link
Contributor

I suspect you are right about the none driver: The dashboard command is not available with the none driver. That said, this error message is terrible and needs fixing.

@tstromberg tstromberg added the r/2019q2 Issue was last reviewed 2019q2 label May 23, 2019
@tstromberg tstromberg added needs-solution-message Issues where where offering a solution for an error would be helpful priority/backlog Higher priority than priority/awaiting-more-evidence. and removed priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. triage/needs-information Indicates an issue needs more information in order to work on it. labels Jul 17, 2019
@sharifelgamal sharifelgamal added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Jul 18, 2019
@tstromberg
Copy link
Contributor

Closing, as this behavior shouldn't exist in v1.4.

@tstromberg tstromberg removed the needs-solution-message Issues where where offering a solution for an error would be helpful label Apr 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/dashboard dashboard related issues help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/backlog Higher priority than priority/awaiting-more-evidence. r/2019q2 Issue was last reviewed 2019q2
Projects
None yet
Development

No branches or pull requests

4 participants