Closed stdedos closed 2 years ago
Folding into https://github.com/mxschmitt/action-tmate/issues/99
We can't do there much probably, since this GitHub Action is only running the official tmate binaries.
I ... am not sure if my issue is "forced termination of actions".
It is clear that "it is taking ages to setup" and that "I cannot connect to it". Nothing related to Github Actions themselves.
It is clear that "it is taking ages to setup" and that "I cannot connect to it".
The root cause is the same as #99's root cause: tmate
and tmate.io have issues at times.
I see. Do you mind if ... I make this more of a conversation ticket?
What is the benefit that tmate brings than an action that would e.g. setup an ssh/bash terminal, and setup the public ssh keys of the user? I am not interested at the web terminal: It didn't appear "as responsive" as I would like it, I don't want to share it with someone, and I would actually prefer to expose as few parts as possible - even when I am debugging.
What is the benefit that tmate brings than an action that would e.g. setup an ssh/bash terminal, and setup the public ssh keys of the user?
You can do that, of course. But since the agents are behind a firewall, you have no way to connect to that Bash/terminal/sshd/whatever.
That is where tmate
comes in: it offers access via a public relay.
Hello there!
I have been using the
mxschmitt/action-tmate@v3
successfully for some time; however, nowadays it is impossible to get a terminal.Preparation is dead-slow:
and after that:
this happens constantly. I was wondering if you'd happen to have some insight into what could be causing this.
I'd prefer if I didn't have to host my own proxy to connect to the instances.