-
-
Notifications
You must be signed in to change notification settings - Fork 306
tmate fails to connect #203
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
Comments
Same story |
That's exactly what it's supposed to do. It stalls the job so you can work, and spits out the command you can use to access the runner now. In your case, you'd run:
|
Thanks for the reply! Yes, this wasn't clear at first, but I eventually figured it out. tmate team: You might consider printing a log message such as "Waiting for SSH client to connect ..." alongside the existing messages. This would make it crystal clear that tmate is pausing execution while waiting to hear from the client. Thanks!
|
New to tmate, but running similar issue as well:
connection is allegedly made, but doesn't actually put me into an interactive shell, and git action continues to print out the connection string every few seconds. am I missing a step? testing using a minimal workflow as follows:
|
It will continue to do that until you actually connect. You can change this behavior by putting
as a tmate action parameter; this will instruct tmate to listen for connections, but in a non-blocking way
|
thanks Aaron! |
Uh oh!
There was an error while loading. Please reload this page.
I tried using tmate for the first time today, with the suggested minimal configuration:
On all my runners, tmate simply went into an infinite loop (and blocked progress on the remaining workflow steps). The output looks like this:
[continues indefinitely, until I cancel the workflow]
In this case, the action was running on a standard
ubuntu-22.04
instance.Thanks!
Aaron
The text was updated successfully, but these errors were encountered: