You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: SSH environment setup is opaque for minutes, then fails with a raw curl timeout #35284
Adding an SSH environment from the desktop client to a cloud server (Ubuntu, x86_64) whose outbound access to github.com is slow. The Add Environment dialog shows a disabled "Adding…" button for ~4 minutes with no other feedback, then fails with:
Could not prepare the SSH environment: Error invoking remote method 'desktop:ensure-ssh-environment':
SshCommandError: curl: (28) Operation timed out after 239291 milliseconds with 3806630 out of 149119656 bytes received
Why this is hard to diagnose
Preparing the SSH environment downloads the t3 release archive (~149 MB) from GitHub on the remote host before the server can start. On a slow host that download takes minutes or times out. During that time the client shows nothing about which stage setup is in (resolving the host, launching the remote server, downloading the archive, verifying the checksum, extracting), so the user cannot tell whether it is hung, what it is doing, or what to fix. The only signal is the final raw curl error, which does not say that t3 itself was being downloaded.
Expected behavior
While preparation runs, the Add Environment dialog should show live setup progress (stage lines / remote setup output) for the target being added, so a slow download is visible as "downloading " instead of an opaque stall, and a failure can be attributed to the right stage.
Desktop client on macOS, remote Ubuntu cloud server over SSH (key auth).
The remote host can reach github.com but at very low throughput; the same host prepares fine when the archive is pre-installed or a mirror is used.
Thanks for writing this up. It asks for new behaviour rather than reporting a defect, so it does not belong in the bug tracker and I'm closing it as not planned here. Feature ideas are discussed in Discussions: please post it there.
Activity
juliusmarminge commentedon Nov 12, 2026
Thanks for writing this up. It asks for new behaviour rather than reporting a defect, so it does not belong in the bug tracker and I'm closing it as not planned here. Feature ideas are discussed in Discussions: please post it there.