Skip to content
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

Open
TmtStss opened this issue Sep 27, 2023 · 5 comments
Open

Can't connect to Sepal with VSCode Remote SSH and Windows11/WSL2 #301

TmtStss opened this issue Sep 27, 2023 · 5 comments

Comments

@TmtStss
Copy link

TmtStss commented Sep 27, 2023

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

Host [ssh.sepal.io](http://ssh.sepal.io/)
  HostName [ssh.sepal.io](http://ssh.sepal.io/)
  User my-username
  Port 443
[email protected]'s password:
3e4ae4af7b40: running
Acquiring lock on /home/sepal-user/.vscode-server/bin/abd2f3db4bdb28f9e95536dfa84d8479f1eb312d/vscode-remote-lock.sepal-user.abd2f3db4bdb28f9e95536dfa84d8479f1eb312d
Found existing installation at /home/sepal-user/.vscode-server/bin/abd2f3db4bdb28f9e95536dfa84d8479f1eb312d...
Checking /home/sepal-user/.vscode-server/.abd2f3db4bdb28f9e95536dfa84d8479f1eb312d.log and /home/sepal-user/.vscode-server/.abd2f3db4bdb28f9e95536dfa84d8479f1eb312d.pid for a running server
Looking for server with pid: 16914
Found running server...

*
* Visual Studio Code Server
*
* By using the software, you agree to
* the Visual Studio Code Server License Terms (https://aka.ms/vscode-server-license) and
* the Microsoft Privacy Statement (https://privacy.microsoft.com/en-US/privacystatement).
*
Checking server status on port 37779 with wget
3e4ae4af7b40: start
SSH_AUTH_SOCK====
DISPLAY====
webUiAccessToken====
listeningOn==37779==
osReleaseId==ubuntu==
arch==x86_64==
vscodeArch==x64==
bitness==64==
tmpDir==/tmp==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
extInstallTime====
serverStartTime====
connectionToken==averylongtoken==
3e4ae4af7b40: end
channel 3: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused
@12rambau
Copy link
Member

why is the tested port 37779 ? I'm not sure it's exposed in SEPAL

@lpaolini
Copy link
Contributor

VS Code Remote SSH extension sets up port forwarding when it connects to a remote.
However, SEPAL ssh gateway doesn't support that, for now.

@TmtStss
Copy link
Author

TmtStss commented Sep 27, 2023

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).

@lpaolini
Copy link
Contributor

I agree it would be a nice feature. We will take your request into consideration.

@TmtStss
Copy link
Author

TmtStss commented Feb 6, 2024

@lpaolini: are there any plans concerning the implementation of this feature?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants