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
Comments
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: |
I found when i restart the sever,the error can be solved.
|
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.
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. |
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. |
It seems this can be closed. |
I agree |
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!
The text was updated successfully, but these errors were encountered: