On the next page define where you want to store the repository on your file system and define some initial settings. On the next page choose which branch should be cloned from the remote repository:

file - File system access to the repository.

https - Hypertext Transfer Protocol Secure can be tunneled through firewalls.

http - Hypertext Transfer Protocol can be tunneled through firewalls.

Typically used for authenticated write access to the repository.

git+ssh - Git over secure shell (SSH) protocol.

Typically used for anonymous read access to the repository. This protocol doesn't provide authentication.

git - The most efficient built-in git protocol (default port 9418).

Password The password used for authentication.

User - The user name used for authentication.

Protocol - One of the protocols described below.

Repository Path - Path to the remote repository or on the file system.

Host - The name of the remote host or empty if cloning from the file system.

This field is automatically synchronized with the other fields.

URI - The complete URI of the remote repository or the path on the file system.

On the first page of the wizard enter the location of the remote repository: Start the import wizard by navigating to File -> Import. Using the Git import wizard you can clone remote repositories using different transport protocols.Īdditionally you may import existing Eclipse projects into your workspace and share the projects with the Git team provider. Working with remote Repositories Cloning remote Repositories

1.3 Pulling (merge or rebase) new changes from upstream.

1.2 Pushing a Local Repository to GitHub.

I then re-uploaded the public key to the server, and then Eclipse’s remote system explorer started working again. So I copied my private and public keys, then used ssh-keygen -f carbon60_id_rsa -m pem to convert the originals to this older style of SSH key. Regenerating an RSA key ( ssh-keygen -t rsa), made the exception go away. The exception only happened for users with key of newer kind ed25519, which outputs this key header:

The root cause was discovered to be the ssh private key mismatch. I then searched for that error which led me to an article that pointed out that SSH key-gen command, at some point, started producing SSH keys that Eclipse (or rather, its Java library that it uses) couldn’t understand. I was like, “how dare you call my private key invalid! I’m using with other programs just fine!” !MESSAGE An error occurred loading the SSH2 private keysĬom.: invalid privatekey: .load(KeyPair.java:664)Īt .load(KeyPair.java:561)Īt .newInstance(IdentityFile.java:40)Īt .addIdentity(JSch.java:406)Īt .addIdentity(JSch.java:366)Īt .(Utils.java:108)Īt .(JSchCorePlugin.java:226)Īt .(JSchProvider.java:46)Īt .(SshConnectorService.java:112)Īt .(SshConnectorService.java:182)Īt .subsystems.AbstractConnectorService$1.run(AbstractConnectorService.java:504)Īt .subsystems.AbstractConnectorService$n(AbstractConnectorService.java:447)Īt .(AbstractConnectorService.java:511)Īt .(SystemFetchOperation.java:311)Īt .(SystemFetchOperation.java:375)Īt .(SystemFetchOperation.java:184)Īt .(AbstractSystemViewAdapter.java:2292)Īt .progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:219)Īt .(Worker.java:63) In there I saw the culprit: !ENTRY 4 0 11:27:14.207 This ancient forum post pointed me to some more debug info in Eclipse’s log file (Help > About > Installation Details : View Error Log). I followed these instructions to make sure Eclipse knew which SSH key to use, but the error didn’t go away. When I tried SSH’ing in with Eclipse I was getting the error Auth Fail So once we disabled password logins, Eclipse wouldn’t work for me anymore. Up until that point, though, I had always used password authentication in Eclipse’s Remote System Explorer.

I then uploaded it to the server, like I described in my previous post (I followed my own instructions). I generated the SSH key locally by using SSH key-gen command on my local machine. Original Setupįirst off, some back story on how I had previously setup the SSH key with the server. I started getting an error saying “Auth fail”.

But once we enabled that, I could no longer use Eclipse to SSH into the server. We recently beefed up security on the server by disabling password logins and instead only allow SSH login with an SSH key. I use the program Eclipse for editing website files on a server.

Eclipse ssh shell enter twice