ssh.tmate.io not working anymore
paolomainardi opened this issue · comments
It seems that is not working anymore since some days, what is happening ?
On my side It's working but I need to wait a lot of times before I can have a working session.
Is ssh.tmate.io down? Who hosts those servers?
Not working for me either.
It is working for me but seems to take an average of 2 minutes to connect
it's working again
No it's not
I can confirm that this has been happening to me inconsistently. I never have a problem connecting to port 22, but it's a dice roll if I get connection reset by peer, connection reset by host, or a connection in. I was thinking adding the -o PubkeyAuthentication=no
flag was helping but it is too inconsistent for me to be sure.
Note: My usage is with travis-ci but it seems to be an issue with tmate.
➜ ~ ssh -vvv $SESSION_KEY@lon1.tmate.io
OpenSSH_8.1p1, LibreSSL 2.7.3
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 47: Applying options for *
debug1: Connecting to lon1.tmate.io port 22.
debug1: Connection established.
debug1: identity file /Users/$USER/.ssh/id_rsa type -1
debug1: identity file /Users/$USER/.ssh/id_rsa-cert type -1
debug1: identity file /Users/$USER/.ssh/id_dsa type -1
debug1: identity file /Users/$USER/.ssh/id_dsa-cert type -1
debug1: identity file /Users/$USER/.ssh/id_ecdsa type -1
debug1: identity file /Users/$USER/.ssh/id_ecdsa-cert type -1
debug1: identity file /Users/$USER/.ssh/id_ed25519 type 3
debug1: identity file /Users/$USER/.ssh/id_ed25519-cert type -1
debug1: identity file /Users/$USER/.ssh/id_xmss type -1
debug1: identity file /Users/$USER/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.1
kex_exchange_identification: read: Connection reset by peer
➜ ~ ssh -vvv $SESSION_KEY@lon1.tmate.io
OpenSSH_8.1p1, LibreSSL 2.7.3
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 47: Applying options for *
debug1: Connecting to lon1.tmate.io port 22.
debug1: Connection established.
debug1: identity file /Users/$USER/.ssh/id_rsa type -1
debug1: identity file /Users/$USER/.ssh/id_rsa-cert type -1
debug1: identity file /Users/$USER/.ssh/id_dsa type -1
debug1: identity file /Users/$USER/.ssh/id_dsa-cert type -1
debug1: identity file /Users/$USER/.ssh/id_ecdsa type -1
debug1: identity file /Users/$USER/.ssh/id_ecdsa-cert type -1
debug1: identity file /Users/$USER/.ssh/id_ed25519 type 3
debug1: identity file /Users/$USER/.ssh/id_ed25519-cert type -1
debug1: identity file /Users/$USER/.ssh/id_xmss type -1
debug1: identity file /Users/$USER/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.1
kex_exchange_identification: Connection closed by remote host
Also seeing issues on my end
It seems that is not working anymore since some days, what is happening ?
cant connect from USA east and west coat
I will most likely move to the same solution.
Hope the maintainer is alright though 🤔 probably gone on holidays 🤷♂️
Enjoy them if this is the case, and thanks for this awesome tool 👍
To be honest, I no longer have an interest in maintaining this project and the servers. I'm going to make a shutdown plan in the upcoming weeks.
To be honest, I no longer have an interest in maintaining this project and the servers. I'm going to make a shutdown plan in the upcoming weeks.
May I ask why? Is it due to server costs? I own a hosting company and may be able to help if so.
Server cost is one thing, but I don't think I care enough about the project. To continue, I think I would want to make significant changes (remove tmux dependency, use Rust) to make the tool not about pair programming but for remote terminal access. I don't have the time/resources to orient the project in a direction that I want to.
Here's a draft for a new plan: https://docs.google.com/document/d/1pGdKgBj0fr5j_DIi44GiyzqZqXnPRWfQlQqVeXrNrhY/edit?usp=sharing
The idea is to make something lower level, some sort of SSH swiss army tool, that the current tmate could be built upon.
@nicm first of all let me just say THANK YOU so much for this project, we as a company are using tmate since years and it helped us so much back in the days and more amid pandemic.
How we, as a community, can help the project to be auto sustainable ? I don’t think it needs more features, it is just perfect as it is.
The ease of use of tmate, combined with the flexibility of tmux, makes it a great remote pair programming solution (if not the best when it comes to terminal-based pair programming session). It is particularly suited for mid/low-bandwidth situation where screen sharing is non viable.
I have played around with the tmate server on Google Cloud Compute Engine this afternoon with medium result (some peers were able to connect, some not).
I think having some tutorial to deploy private tmate server on regular cloud providers would be a great benefit to the project and its community (myself included), and could help making it sustainable while having fewer pieces to take care of on your side. I could help with that, however my knowledge is limited.
Let me join paolomainardi in saying thank you 🎉
I'll think about a plan in the upcoming week
Hey @nviennot I just reached out via email to see if I can help you with some server space and bandwidth. I love tmate and I use it a lot. I'd hate to see the service go away.
We can sponsor the project too, bandwidth and all the rest.
Server cost is one thing, but I don't think I care enough about the project. To continue, I think I would want to make significant changes (remove tmux dependency, use Rust) to make the tool not about pair programming but for remote terminal access. I don't have the time/resources to orient the project in a direction that I want to.
Here's a draft for a new plan: https://docs.google.com/document/d/1pGdKgBj0fr5j_DIi44GiyzqZqXnPRWfQlQqVeXrNrhY/edit?usp=sharing
The idea is to make something lower level, some sort of SSH swiss army tool, that the current tmate could be built upon.
I too, like others have said, love tmate! I'm not much help at maintaining the project in the way of adding the new features people want but we can provide hosting as well at no cost to you if necessary. We've provide up to 25 Gbps bandwidth and plenty of resources for many connections in our main location, we also own all our own hardware hosted in our privately owned facilities around the world. Let me know if you need anything and hopefully we can help in that regard!
I read the plan you posted as well and personally I like tmate just the way it is, just with the bugs patched. Though I don't really mind more features or changes as long as there are sane defaults, like now.
That's very generous, thank you, I'll think about it
Thank you very much for this project :-)
I just wanted to say I love this project. I've been using tmate for years as a pair programming solution. I'm very happy with the project "as-is" and I'd be sad to see it go away. That said, thank you so much for the work on this project it's made my (and also the folks I pair with) life so much easier.
I stumbled across this thread after I wasn't able to reach my clients anymore :) Same here - the tool is just perfect as is. Sad to hear your plans, but understandable. If this project and it's infrastructure could proceed as is, that would be so great. If my help is needed for whatever - ping me.
I just wanted to say I love this project. I've been using tmate for years as a pair programming solution.
I also use it constantly, and probably even paired with @tenderlove using tmate at some point!
I just want to point out that running your own tmate server is trivial. I did for the YAML dev crew. Here's how:
On a public server run:
curl -s -q https://raw.githubusercontent.com/tmate-io/tmate-ssh-server/master/create_keys.sh | bash
docker run \
-d \
--name=tmate-server \
--cap-add SYS_ADMIN \
-v "$PWD"/keys:/keys \
-e SSH_KEYS_PATH=/keys \
-p 12345:12345 \
-e SSH_PORT_LISTEN=12345 \
-e SSH_HOSTNAME=tmate.yaml.io \
-e USE_PROXY_PROTOCOL=0 \
tmate/tmate-ssh-server:prod
Then users can alias tmate like so:
alias tmate='\tmate -f <(
echo set -g tmate-server-host tmate.yaml.io
echo set -g tmate-server-port 12345
echo set -g tmate-server-rsa-fingerprint SHA256:80bgrhZV4v7Vazw0hxLdkciNFlyAGOYKT8i/H4scsJI
echo set -g tmate-server-ed25519-fingerprint SHA256:ydkiIFYzQsKp6hry2+34bdYumPGxSrOcqbfJZGMLbcs
echo source-file ~/.tmux.conf
)'
That's an actual running tmate server in a docker container on a digitalocean vm. I'll leave it running for a few days. Go ahead an try it out. What could possibly go wrong?!
I know this isn't a perfect solution for replacing ssh.tmate.io but it's better than nothing. I've also used it in work situations behind firewalls where the company didn't trust the tmate.io server.
Credit to: https://blog.fgribreau.com/2021/02/how-to-setup-your-own-tmate-server-with.html
I just wanted to say I love this project. I've been using tmate for years as a pair programming solution.
I also use it constantly, and probably even paired with @tenderlove using tmate at some point!
I just want to point out that running your own tmate server is trivial. I did for the YAML dev crew. Here's how:
On a public server run:
curl -s -q https://raw.githubusercontent.com/tmate-io/tmate-ssh-server/master/create_keys.sh | bash docker run \ -d \ --name=tmate-server \ --cap-add SYS_ADMIN \ -v "$PWD"/keys:/keys \ -e SSH_KEYS_PATH=/keys \ -p 12345:12345 \ -e SSH_PORT_LISTEN=12345 \ -e SSH_HOSTNAME=tmate.yaml.io \ -e USE_PROXY_PROTOCOL=0 \ tmate/tmate-ssh-server:prod
Then users can alias tmate like so:
alias tmate='\tmate -f <( echo set -g tmate-server-host tmate.yaml.io echo set -g tmate-server-port 12345 echo set -g tmate-server-rsa-fingerprint SHA256:80bgrhZV4v7Vazw0hxLdkciNFlyAGOYKT8i/H4scsJI echo set -g tmate-server-ed25519-fingerprint SHA256:ydkiIFYzQsKp6hry2+34bdYumPGxSrOcqbfJZGMLbcs echo source-file ~/.tmux.conf )'
That's an actual running tmate server in a docker container on a digitalocean vm. I'll leave it running for a few days. Go ahead an try it out. What could possibly go wrong?!
I know this isn't a perfect solution for replacing ssh.tmate.io but it's better than nothing. I've also used it in work situations behind firewalls where the company didn't trust the tmate.io server.
Credit to: https://blog.fgribreau.com/2021/02/how-to-setup-your-own-tmate-server-with.html
How did you manage to get that to work? I set up one and tried every combination of things I could to no avail. I made an issue about it here but got no response that I haven't already tried. I tried your server as well and the same exact issue exists on tmate on Debian 10 and 11 using both tmate from apt and the latest tmate binary from tmate.io. It works on Ubuntu but not Debian.
EDIT: It works on some Debian 11 systems and Ubuntu but not Debian 10. Debian 10 repo has version 2.2 and Debian 11 has 2.4, however installing binary 2.4 from tmate.io on Debian 10 does NOT fix the issue. :/ I also don't know why it doesn't work on all Debian 11 systems since it's the same tmate version on both.
@ELECTROHAXZ
Yes sorry, I think this only works using the version 2.4 tmate command. In the past I had to run 3 different docker container servers for 2.2, 2.3 and 2.4.
I'll try a few things and report back later.
This worked for me on my ubuntu 20.04 host:
> wget https://github.com/tmate-io/tmate/releases/download/2.4.0/tmate-2.4.0-static-linux-amd64.tar.xz
> tar xf tmate-2.4.0-static-linux-amd64.tar.xz
> export PATH=tmate-2.4.0-static-linux-amd64:$PATH
> alias tmate='\tmate -f <(
echo set -g tmate-server-host tmate.yaml.io
echo set -g tmate-server-port 12345
echo set -g tmate-server-rsa-fingerprint SHA256:80bgrhZV4v7Vazw0hxLdkciNFlyAGOYKT8i/H4scsJI
echo set -g tmate-server-ed25519-fingerprint SHA256:ydkiIFYzQsKp6hry2+34bdYumPGxSrOcqbfJZGMLbcs
echo source-file ~/.tmux.conf
)'
> tmate
@ELECTROHAXZ Yes sorry, I think this only works using the version 2.4 tmate command. In the past I had to run 3 different docker container servers for 2.2, 2.3 and 2.4. I'll try a few things and report back later.
Yeah I figured it's something with versions. I just don't get why it works on some systems but not others. I tried using version 2.4 and on some systems it works, others (most) do not. How did you run other versions of docker container? Mine seems to only work on 2.4.
@nviennot sorry for chasing, just asking some updates on your side if the current service will be back as it exists now or if it’s better to plan some other strategies on our side to self host the tmate server part.
I think that something like https://opencollective.com/ or Patreon to fund this and the next project would be a way to materialize our help in a better way, at least for the funding part.
With all these messages, i can't turn off tmate servers, it would be tragic.
I'll restore the service quality this week, and open sponsoring to help keeping it running.
that's probably the best news i'll ready this week...
thank you very much nicolas, much appreciated!
and let us know when a sponser page is setup, i'm ready to help :)
How did you run other versions of docker container? Mine seems to only work on 2.4.
This was a few years ago. The 2.2 server image seems no longer available on https://hub.docker.com/r/tmate/tmate-ssh-server/tags
How did you run other versions of docker container? Mine seems to only work on 2.4.
This was a few years ago. The 2.2 server image seems no longer available on https://hub.docker.com/r/tmate/tmate-ssh-server/tags
Darn, that sucks because 2.2 is the newest version available in Debian 10 repos, and Debian 10 is still supported until August at least with security updates for longer.
Today I tested https://upterm.dev/ and it is a very promising alternative to tmate, just in case.
tmate has been absolutely amazing for my community of 2k+ members helping each other running nodes on our project. It completely removes the trust issues between strangers inside a community and I can't thank you enough to consider ways to help keep the project alive.
I'm very appreciative that you've decided to keep the servers up!
Has this issue been resolved for others? I'm still getting these messages when trying to start tmate:
Reconnecting...
Connecting to ssh.tmate.io...
Error connecting: Socket error: disconnected
I am also very appreciative of keeping this project alive, it has helped me out in many ways.
I am also still receiving the same issues in starting tmate:
Connecting to ssh.tmate.io...
Error connecting: Socket error: disconnected
Reconnecting... (Error connecting: Socket error: disconnected)
Connecting to ssh.tmate.io...
So the issue does not seem to be resolved as of right now.
It would be great to see this project continue. Myself and my colleagues use the GitHub Action (https://github.com/mxschmitt/action-tmate) to debug failed GitHub Actions runs for our CI. It has been a life saver in several instances, making it much easier to understand the failure and how to fix it.
We hope this project can continue because its genuinely a tool that has helped us save several hours of frustration
Agreed, I am very sad that this no longer works.
seems like upterm is deprecated as well. I found a working alternative for whose still interested. The free tier is 45 minutes sessions. https://duckly.com/
I'm getting on it, hold tight my friends
I've added some server capacity. The system should be able to hold up to 25,000 tmate clients. Right now there's 4,000 connections.
No rush, but will there be a new release made?
No rush, but will there be a new release made?
For? Its working again here. Very happy about that as the project I help support, uses it a lot.
No rush, but will there be a new release made?
For? Its working again here. Very happy about that as the project I help support, uses it a lot.
For packaging the updates for GNU Guix