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

Couldn't connect to TextMate! #2

Closed
SymphonyPy opened this issue Jun 26, 2018 · 6 comments
Closed

Couldn't connect to TextMate! #2

SymphonyPy opened this issue Jun 26, 2018 · 6 comments

Comments

@SymphonyPy
Copy link

SymphonyPy commented Jun 26, 2018

I am using this on Ubuntu and meet this problem.
root@VM-42-3-ubuntu:~# rmate -p 52698 ping.c
Couldn't connect to TextMate!
It worked when I first used this yesterday, but the error appeared today.
Is there any way to solve this? Thank you!

@broadtoad
Copy link

rmate also abruptly stopped working for me as well - was working fine before (apart from occasional saving issues).

Tried bash and python version and receive same error: Couldn't connect to TextMate!

@Kmyu1k
Copy link

Kmyu1k commented Aug 14, 2018

I found when i restart the sever,the error can be solved.
here is my step:

  1. in vscode press F1 and select Remote:Stop Server
  2. in vscode press F1 and select Remote:Start Server

@salmr0
Copy link

salmr0 commented Aug 24, 2018

I am having the same issue. Looks like the socket is left open on the server side. I quit everything and logged out of everywhere. Then I ssh back into the server (after disabling the SSH port forwarding of port 52698) and I see this. There should be no port using 52698 as I disables ssh port forwarding but some how the socket is still there lingering.

netstat -tnl |grep 52698 
tcp        0      0 127.0.0.1:52698         0.0.0.0:*               LISTEN     

For me this is why I get the "Couldn't connect to TextMate!" message because the port is in use and I can't get rid of it. Don't have root access to server so I can't get the PID to kill it.

@salmr0
Copy link

salmr0 commented Aug 24, 2018

Got one of the admins(root) to run netstat with "-p" option for me. Looks like some other user is using that port (maybe other rmate user). That is why I can not use it and get the "Couldn't connect to TextMate!".

So no issue. I will just pick a different port. Sorry for the spam.

@rspeed
Copy link

rspeed commented Dec 31, 2018

It seems this can be closed.

@sclukey
Copy link
Owner

sclukey commented Dec 31, 2018

I agree

@sclukey sclukey closed this as completed Dec 31, 2018
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

6 participants