-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
macOS host: session dies as soon as I connect (transport: Error while dialing dial unix /Users/runner/.upterm/xxxxxxxxxxx.sock: connect: connection refused") #11
Comments
|
I see that on Linux, you use a fixed version of upterm: Lines 21 to 22 in 461637e
whereas on macOS you simply install whatever upterm's Homebrew tap has: Lines 24 to 25 in 461637e
So maybe that's caused by a regression in upterm... |
OK, so I forked the action and replaced the So it is definitely a regression in upterm, I would think. |
I run into the same issue. I would help perhaps if I could pass the version to install to the action |
This might be an issue with the ssh key type. See #9 for more details. There's also some notes about RSA keys in the README of upterm. The workaround is to use an Ed25519 key. |
Here's the example of a successful connection: https://github.com/lhotari/github-actions-debug/runs/5640278819?check_suite_focus=true#step:3:111 After the client disconnects, the log output is similar to what is described in this issue. I tested with |
I got this error the first time I tried it, but it turns out I hadn’t configured my SSH public key in my GitHub profile. Go to your account settings and click on “SSH and GPG keys” in the navigation bar, then click “New SSH key” and paste the contents of your Unfortunately I ran into another issue:
which I suspect is due to the key type not being supported as @lhotari suggested in the earlier post. Now I just need to figure out how to generate a SHA-1 or Ed25519 key… |
Hi!
Thanks for this action. I'm trying it out for the first time on
macos-10.15
GHA runners, and as soon as Issh
from my machine, the upterm session seems to die. Locally I simply get:and in the GitHub Actions log (example: https://github.com/phil-blain/github-actions-debug/runs/5293251543?check_suite_focus=true#step:3:96)
The text was updated successfully, but these errors were encountered: