I am struggling to connect my Eclipse Remote environment to my Google cloud Instance.
I have generated a public and private key with ssh-keygen on my mac and stored them in the ~/.ssh folder. I copied the public key to the google cloud using the metadata and added the key to the ssh keys listed. I also added the private key to eclipse in the SSH2 settings. Trying to connect give me error: Failed to connect sshd on " my ip-address".
The strange thing is that Filezilla can connect in this way, but `i would like the comfort from Eclipse. Can somebody help me with this problem??
If you were able to access by sftp with Filezilla that means that your ssh-keys are correct, I recommend you put the ssh-key in the metadata section of the instance, here is the link with the steps.
To connect with eclipse:
Try the Remote System Explorer (RSE). It's a set of plug-ins to do exactly what you are looking for.
RSE may already be included in your current Eclipse installation. To check in Eclipse Indigo go to Window > Open Perspective > Other... and choose Remote System Explorer from the Open Perspective dialog to open the RSE perspective.
To create an SSH remote project from the RSE perspective in Eclipse:
Define a new connection and choose SSH Only from the Select Remote
System Type screen in the New Connection dialog.
Enter the connection information then choose Finish.
Connect to the new host. (Assumes SSH keys are already set up.)
Once connected, drill down into the host's Sftp Files, choose a
folder and select Create Remote Project from the item's context
menu. (Wait as the remote project is created.)
If done correctly, there should now be a new remote project accessible from the Project Explorer and other perspectives within eclipse. With the SSH connection set-up correctly passwords can be made an optional part of the normal SSH authentication process. A remote project with Eclipse via SSH is now created.
Related
I am using Eclipse since years (Ubuntu and Windows in parallel), and the projects are growing...
However, I am using many remote GIT repositories with SSH Keys that are protected by passphrases.
My problem is that Eclipse asks me for all passphrases every time I want to push to a server, which is very annoying. And I can't find a way to tell Eclipse which SSH Key belongs to which host.
Can anybody help me?
I can't get my Eclipse 3.8 (Ubuntu installation), RSE/TM plugin 3.4 or 3.5 connect with google-compute-engine/debian-7-wheezy-v20140606. I have tried to use vm IP directly and also alias method that gcloud compute command line utility provides. Both work from command line but RSE ends up authentication error. It seems that RSE ignores ~/.ssh/config that alias method uses.
Do anyone know what settings/procedure should I use for this connection?
I found how to make settings.
Supposing that your connection name is GCE-1:
Open Remote System Explorer perspective.
Select GCE-1 from Remote System Explorer window.
Right click -> Properties.
Select Host at the left panel of "Properties for GCE-1" window.
Click Configure proxy settings at the Host panel of "Properties for GCE-1" window.
Navigate General -> Network Connection -> SSH2.
Select General tab.
Click Add Private Key button.
Navigate to ~/.ssh.
Select google_compute_engine and click OK and OK.
Note that GCE command line tools create this file by default.
Done! Now you can navigate e.g. your Sftp Files below GCE-1 Within Remote Systems window.
Every time I want to run my project on the remote server, I need to export it from Eclipse as a jar file, to transfer the file from my local machine to the remote server using WinSCP and then to use Putty to run it on the remote server. I am wondering is there a more suitable way of handling this, e.g. an Eclipse plugin that allows me to perform this straight from Eclipse.
This functionality is present in Eclipse, called Remote Systems Explorer.
Open the Remote Systems view by going to Window -> Show View -> Other....
Then right click in this view and select on New connection....
Select SSH Only as remote system type and click Next.
Fill in the necessary information such as hostname and connection name and click Finish.
Select the Connector node you just created from the Remote Systems view and choose Connect.... Enter your credentials and press Ok.
If you managed to log in, you will see a green arrow on the node indicating you are connected.
You can right click either Shells or Terminals and choose Launch Shell/Terminal. A new Remote Shell or Terminal should appear where you can type in commands.
It is also possible to remotely create files, open/edit and save them from within Eclipse.
More documentation can be found in the Eclipse RSE manual.
my project source code is in unix, we are using CM synergy source control for code checkin/chech out files. we update the files using vi editor. Pls help in how to set up eclipse in windows system and then connect to the code server and edit the files.
You could install the Remote System Explorer framework, that allows opening files from a remote server, and also gives shell access to the remote server. For anything more specific, I'm not sure whether a free solution exists.
I experienced some problems accessing remote file systems with the Remote System Explorer Plugin, the FTP session was closed unexpectedly. I recommend for linking in your local projects remote sites Aptana Eclipse Plugin.
Hey, I am using Eclipse (while running Ubuntu 10.10) and would like to connect to a remote git. Normally I would use the egit plugin, but now I need to connect over ssh with keyfile.
Unfortunately egit has no "with keyfile" option, is there a way to connect to my repository with my keyfile?
Is there a "hidden" way to make Eclipse to pass parameters (-i keyfile) to ssh or something?
http://wiki.eclipse.org/EGit/User_Guide/Remote - I had to manually load my existing key in the "Key Management" tab.
I don't know anything about egit. But what you usually do is:
Start ssh-agent (mine is automatically started, when my window manager starts, so you have to google a bit how to setup it)
Run ssh-add [your key]
Use git over ssh as usual. It won't ask you for any passwords, since ssh-agent takes care of it.
HTH