macOS host: session dies as soon as I connect (transport: Error while dialing dial unix /Users/runner/.upterm/xxxxxxxxxxx.sock: connect: connection refused")
See original GitHub issueHi!
Thanks for this action. I’m trying it out for the first time on macos-10.15
GHA runners, and as soon as I ssh
from my machine, the upterm session seems to die. Locally I simply get:
$ ssh szq1wc1331uu9SXcR9DY:MTAuMjQ0LjAuNjU6MjI=@uptermd.upterm.dev
Connection closed by 157.230.199.75 port 22
and in the GitHub Actions log (example: https://github.com/phil-blain/github-actions-debug/runs/5293251543?check_suite_focus=true#step:3:96)
Creating a new session. Connecting to upterm server ssh://uptermd.upterm.dev:22
Created new session successfully
Entering main loop
=== SZQ1WC1331UU9SXCR9DY
Command: tmux new -s upterm -x 132 -y 43
Force Command: tmux attach -t upterm
Host: ssh://uptermd.upterm.dev:22
SSH Session: ssh szq1wc1331uu9SXcR9DY:MTAuMjQ0LjAuNjU6MjI=@uptermd.upterm.dev
=== SZQ1WC1331UU9SXCR9DY
Command: tmux new -s upterm -x 132 -y 43
Force Command: tmux attach -t upterm
Host: ssh://uptermd.upterm.dev:22
SSH Session: ssh szq1wc1331uu9SXcR9DY:MTAuMjQ0LjAuNjU6MjI=@uptermd.upterm.dev
Error: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial unix /Users/runner/.upterm/szq1wc1331uu9SXcR9DY.sock: connect: connection refused"
Usage:
upterm session current [flags]
Aliases:
current, c
Examples:
# Display the current session defined in $UPTERM_ADMIN_SOCKET
upterm session current
# Display the current session with a custom path
1
upterm session current --admin-socket ADMIN_SOCKET_PATH
Flags:
--admin-socket string admin unix domain socket (required)
-h, --help help for current
time="2022-02-22T18:52:18Z" level=fatal msg="rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /Users/runner/.upterm/szq1wc1331uu9SXcR9DY.sock: connect: connection refused\""
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Error response from daemon: dial unix docker.raw.sock: connect
I have tried with the latest version of my channel (Stable or Edge) ... from daemon: dial unix docker.raw.sock: connect: connection refused.
Read more >connection error: desc = "transport: dial unix:///var/run/docker ...
For macOS users: if you get the macOS equivalent: ERROR: dial unix docker.raw.sock: connect: connection refused. You can restart Docker with ...
Read more >connection error: desc = "transport: dial unix /var/run/docker ...
sock : connect: connection refused”: unknown.” when trying to restart existing containers, run new containers, docker top, docker exec, and ...
Read more >rsync freezes in macos ventura - Unix & Linux Stack Exchange
I've been having all sorts of issues with SSH related tools since upgrading to Ventura. Adding the following lines to my ~/.ssh/config file ......
Read more >unison-manual
Unison runs on both Windows (95, 98, NT, 2k, and XP) and Unix (OSX, Solaris, Linux, ... Unison works between any pair of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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
macos-latest
, this was my workflow yaml: https://github.com/lhotari/github-actions-debug/blob/22a32d44acbcf23647eae1ef9ce31a48a8f7fbf7/.github/workflows/ci.ymlI 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
~/.ssh/id_rsa.pub
file.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…