Open spikecurtis opened 7 months ago
We identified that the issue was the proxy command failed because the header command provided to the plugin was failing.
I wonder if it is possible to surface a better error instead of just "server closed", but I think it depends on whether the error returned by the Gateway API contains that information in some way or if it really is just "server closed".
If it does not, maybe there is something else we can do to suss out problems with the header command, like running SSH ourselves just as a sanity check before we call out to Gateway's stuff.
Renamed the issue to somehow surface an error from running the proxy command. We had another issue where it was failing because the agent was shutting down but this was not being shown directly to the user.
Some users are reporting trouble connecting to their workspaces, and receive an error "Server closed connection during identification exchange" on the "Choose IDE and project for workspace ... " screen.
Stack trace is: