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

When I click the EON device in Workbench, nothing happens. I've tried uninstalling, etc but console never appears #73

Open
2 tasks
tjcastle01 opened this issue Feb 6, 2020 · 6 comments

Comments

@tjcastle01
Copy link

  • Your Workbench.app version is 0.1.5. Please verify you're using the latest Workbench.app version
  • I have searched the issues of this repo and believe that this is not a duplicate

  • Any relevant information from devtools? (CMD+ALT+I on macOS, CTRL+SHIFT+I elsewhere):

Issue

  • Workbench version: undefined "0.1.5"

  • OS ARCH VERSION: darwin x64 15.6.0

  • Electron: 2.0.17 LANG: undefined

  • SHELL: /bin/bash TERM: undefined

~/.workbench.js contents
        
          {
  "eonSshKeyPath": "",
  "config": {
    "shell": "/bin/bash"
  },
  "keymaps": {},
  "windowBounds": {
    "width": 800,
    "height": 800
  },
  "clientId": "1d334150-4885-11ea-9de2-75100c47fd88"
}
        
      
@cowanhm
Copy link

cowanhm commented Apr 5, 2020

Found the problem. Can't use private key in "/.ssh" directory.

Backup .ssh dir, "remove all" keys in EON, reinstall WB

@tapethis
Copy link

Added pub keys to github, pasted priv keys to openpilot_rsa in .ssh, and added git username to c2, and workbench shows the EON IP, but when I click on it nothing happens. Before it used to give the error permission denied. OP v0.8.3

@ErichMoraga
Copy link

Be sure to follow the pinned instructions in the official OP Discord's #installation-help channel.

@tapethis
Copy link

Have done all of that... and it still does nothing. I have tried to uninstall and deleted the folder from appdata and reinstalled as well. Same network w. 255.255.255.0

@hjsspin
Copy link

hjsspin commented Jun 21, 2021

Tonight, I happen to meet with the same situation. Later, I found I can however access c2 from another computer, with the ssh keys at the first set. I haven't check it but it seems to me that workbench reconizes only the first set of ssh keys in my case. May be someone can check it out.

@jason-something
Copy link

I ran into this issue also. I assumed I had done something incorrectly with the keys however I was able to log in with Putty just fine. I've ran into issues with certain versions of node.js / npm before, perhaps there is some issue? I dunno.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants