rsub with sublime and ssh connection refusual

问题:

I am trying to use rsub to create tunnel in ssh to sublime text, I run the command rmate .profile but i get the following response. I am using wateroof to open the ports 52968 on 1p4 and ip6, I followed the insturctions here and its just not working

I am running osx on my local machine and ubuntu 12.04 on my remote machine I am ssh into on digitalocean

root@anderskitson:~# rmate .profile
/usr/local/bin/rmate: connect: Connection refused
/usr/local/bin/rmate: line 186: /dev/tcp/localhost/52698: Connection refused
Unable to connect to TextMate on localhost:52698

回答1:

I was having the same problem.

Let remoteHost = the IP or hostname of the machine you're attempting to ssh to.

I ran ssh -R 52698:localhost:52698 remoteHost from my local machine, after whice rmate .profile on remoteHost worked.

That led me to determine that ~/.ssh/config on my local machine was incorrect.

I set ~/.ssh/config to look like this:

Host remoteHost
  RemoteForward 52698 localhost:52698

It's been working solidly since I made that change.

回答2:

For anyone getting this same error using PuTTy on Windows, this commenter gives great instructions:

1. In PuTTy's config window, nagivate to the Connection > SSH > Tunnels pane
2. In the "Source Port" field, type 52698
3. In the "Destination" field, type 127.0.0.1:52698
4. Select the "Remote" and "Auto" radio buttons
5. Click the "Add" button
6. Go to the Session pane and save if you want to preserve these settings.

Here's an image which does the explaining visually:

回答3:

I had the same issue and here is what works for me. If you have multiple servers you want this to work for, do the following as exactly shown here:

Host *
  RemoteForward 52698 localhost:52698

I consulted this link: configure SSH config file and realized you can use * in config file.

Wildcards are also available to allow for options that should have a broader scope.

回答4:

I had the same problem and fixed with replacing the HOSTNAME with the actual IP-Address when connecting:
e.g.: ssh [e-mail] to ssh pi@192.168.1.1

回答5:

I was trying to set this up for the first time using VS Code and got the generic "Connection refused" error even though my configuration seemed fine. It turned out to be because I hadn't reloaded the IDE after installing the rmate extension (Remote VSCode). Make sure that the rmate server is active on your local machine, whatever IDE you're using.

回答6:

I had the same problem and gone through most of the blogs, I did everything that was told. At last, I found myself that textmate or submile editors are closed(force quit), this caused the problem.

回答7:

For example my SSH config ~/.ssh/config file to connect with DigitalOcean with Remote Forward looks like:

Host DigitalOcean
  Hostname xxx.xxx.xxx.xxx
  User username
  RemoteForward 52698 localhost:52698

and is called in a terminal

ssh DigitalOcean

rmate then connects fine with my local Atom editor

回答8:

rmate stopped working for no apparent reason. Turns out I had tripped the 'man in the middle' check. I saw this warning when doing ssh --

\@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

In my case, this warning was expected so I ignored it. This may not apply for you, so verify host identity. Didn't realize this line at the end of the warning --

Port forwarding is disabled to avoid man-in-the-middle attacks.

No wonder rmate stopped working. Verifying host identity and then clearing out offending entry from ~/.ssh/known_hosts made the warning go away and rmate started working again.