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

SSH into multiple distinct VM's causes authentication issues #48

Closed
alex-barylski opened this issue Jul 27, 2017 · 1 comment
Closed

Comments

@alex-barylski
Copy link

First off, thank you for your efforts, this plugin has been awesome :)

One issue however, is that NetBeans or the plugin when SSH'ing into multiple VM's in the same NB instance causes the IDE to lose reference to the private key? The key exists BUT the plugin just can't seem to find it? I can usually log into one VM but when I spin up another login, and switch back to the previous VM this issue pops up.

I get this screen when trying to SSH:

nbauth1

The work around (for me) is to find the following file:

C:\Users\YOU\AppData\Roaming\NetBeans\8.X\config\Preferences\org\netbeans\modules\dlight\nativeexecution.properties

Which contains something like:

org.netbeans.modules.nativeexecution.api.util.Authentication_vagrant@127.0.0.1\:2222=C:\\Users\\ME.DOMAIN\Desktop\\Projects\\COMPANY\\PROJECT\\.vagrant\\machines\\default\\virtualbox\\private_key
org.netbeans.modules.nativeexecution.api.util.Authentication_vagrant@127.0.0.1\:2222.methods=gssapi-with-mic#1,publickey#1,keyboard-interactive#1,password#1
org.netbeans.modules.nativeexecution.api.util.Authentication_vagrant@127.0.0.1\:2222.timeout=10
org.netbeans.modules.nativeexecution.api.util.ConnectionManager_connection.history_0=vagrant@127.0.0.1:2222
vagrant@127.0.0.1\:2222_allGroups=1000
vagrant@127.0.0.1\:2222_groupId=1000
vagrant@127.0.0.1\:2222_userId=1000

If I clear this file and save - close NetBeans and re-open I then get this screen which allows me to select the private key:

nbauth2

Am I doing something wrong? I am using Windows 10 - but I had the same issue with Ubuntu.

Any ideas?

@junichi11
Copy link
Owner

Sorry, I'm not sure about that at the moment. Although I cannot promise anything, I try to look at it later...

If there is a problem, please try to use "remote terminal" manually.
nb-vagrant-issue48

@alex-barylski alex-barylski closed this as not planned Won't fix, can't repro, duplicate, stale Jun 25, 2022
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

2 participants