-
Notifications
You must be signed in to change notification settings - Fork 46
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
Can't connect to Sepal with VSCode Remote SSH and Windows11/WSL2 #301
Comments
why is the tested port 37779 ? I'm not sure it's exposed in SEPAL |
VS Code Remote SSH extension sets up port forwarding when it connects to a remote. |
Thank you for the clarification. Is there a plan to support this feature in the future ? I don't know how many of the Sepal users use Sepal for dev purposes like me (hence how big is the incentive), but it would help a lot to have it (and alike, e.g. #251). |
I agree it would be a nice feature. We will take your request into consideration. |
@lpaolini: are there any plans concerning the implementation of this feature? |
I have a Windows 11 computer with a Windows Subsystem for Linux (WSL2). I use VS Code as code editor, and would like to connect to Sepal using the convenient Remote SSH extension. Here is the content of my C:/Users/my_username/.ssh/config file. I get a prompt asking for my password and then it tries to connect indefinitely or refuses connection.. I can access Sepal through ssh directly (e.g. for scp file transfer) without issue. I also tried implementing this popular fix, without success. So I wonder if the issue is not with Sepal.
See also: Connect to Sepal host with VSCode Remote SSH on Windows 11/WSL2
The text was updated successfully, but these errors were encountered: