Open hojaeklee opened 11 months ago
Experiencing similar issues here regarding inability to connect to host that requires a ProxyJump
Yes I have the same issue
Me too... Any reason why Cursor has moved away from using native SSH extension in VSCode? It was working nicely before... Otherwise thanks for a great product
I can give some more detailed info. Suppose we have an entry in the ssh config file
Host test
HostName example.com
ProxyCommand ssh -W %h:%p example.com
User me
(It is a bit of a convoluted example as it is using the host example.com
as a jump server to itself). I can connect to this fine in VS Code and Cursor.
My problem is that I need to spawn a shell so that I can ensure the PATH is set correctly. It is a little technical and boring why I need to do this, but please accept that this is critical to me and my team being able to use Cursor. So I have a config like
Host test
HostName example.com
ProxyCommand bash -c 'export PATH=$PATH:/usr/local/bin; ssh -W %h:%p example.com'
User me
This works on VS Code but not on Cursor. It may seem like an edge case, but I would say that whatever works in a shell or VS Code should ideally also work in Cursor, as there may be other cases that break.
Any update on this issue? I'm hitting this now trying to connect through Google Cloud IAP (using gcloud). Thanks
have the same issue
I'm having the same issue
Hello to the wonderful developers!
I am a student who primarily uses my school's HPC, which often involves remote ssh-ing to a compute node (e.g. node with GPU). I achieve this by adding a
ProxyCommand
to my ssh configuration file, as shown below:I noticed I can remote-ssh to my login-node, but cannot do so to the compute-node (error screenshot below). I have updated Cursor to 0.8.2 but the issue seems to persist.
Any ideas on how to fix this would be amazing (and allow me to switch from VSCode to Cursor full time!)