randy3k / RemoteSubl

Use rmate with Sublime Text, an improved fork of rsub.
331 stars 20 forks source link

No error message, but sublime doesn't open the File #12

Open blutjens opened 4 years ago

blutjens commented 4 years ago

Hello, Thanks for the great tool!

I am running $rmate tst.py , and don't get any error message, but my sublime does not open any file. Would you be able to help me, please?

I have installed RemoteSubl in sublime text 3.1..1 on my local workstation, that runs Windows 10. I have installed rmate on my remote workstation in /home/users//rmate (because I don't have access to /usr/local/bin/). I have also added /home/users//rmate to the PATH environment variable and ran $chmod a+x /home/users//rmate.

Thank you! Björn

permissionx commented 4 years ago

Same problem. No any responses, and sublime not open.

chrwalz commented 4 years ago

Same issue on windows 10 with OpenSSH, however works as expected when using putty.

randy3k commented 4 years ago

You want to check if the port is being forwarded.

chrwalz commented 4 years ago

Just to provide some more information for the OpenSSH in windows that I'm experiencing:

I am connecting using: ssh -p 22 -R 52698:localhost:52698 -i privateKeyLocation -v user@host With the console output being:

~$ rsub test.txt
debug1: client_input_channel_open: ctype forwarded-tcpip rchan 3 win 2097152 max 32768
debug1: client_request_forwarded_tcpip: listen localhost port 52698, originator 127.0.0.1 port 49846
debug1: getsockopt TCP_NODELAY: Invalid argument
debug1: connect_next: host localhost ([::1]:52698) in progress, fd=7
debug1: channel 1: new [127.0.0.1]
debug1: confirm forwarded-tcpip
debug1: channel 1: connected to localhost port 52698
debug1: channel 1: free: 127.0.0.1, nchannels 2
~$

with nothing opening in sublime.

Thanks!

ayalon commented 4 years ago

I fixed it on Windows 10. The issue is the Bash Shell script. I simply switched to the python version of rmate: https://github.com/sclukey/rmate-python

After adding these lines to ~/.ssh/config it worked also with Windows OpenSSH.

But I have to admit, that I updated the Windows OpenSSH binaries to the latest version:

Host *
  RemoteForward 52698 127.0.0.1:52698

Do not use localhost:52698 it does not work. It has to be 127.0.0.1:52698

gabrer commented 4 years ago

I had the same problem on Windows 10. Then, thanks to @ayalon, I've just modified connection command as follows and it worked:

ssh -R 52698:127.0.0.1:52698 usr@ipadd

I've used 127.0.0.1:52698 rather than localhost:52698.

sanjiblamichhane commented 3 years ago

I have the same issue but on mac. I tried putting the following instruction on config file but did not work. Any suggestion specific to mac?

Host * RemoteForward 52698 127.0.0.1:52698

xiaoyunguo commented 3 years ago

I have the same issue on Mac as well. It was working with RemoteForward 52698 127.0.0.1:52698, but after one lost connection session, I can't open any file any more.