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

VSCode remote connection to working ssh fails with VSCode / MacOSX #2282

Closed
RokuKent opened this issue Feb 1, 2020 · 3 comments
Closed

VSCode remote connection to working ssh fails with VSCode / MacOSX #2282

RokuKent opened this issue Feb 1, 2020 · 3 comments

Comments

@RokuKent
Copy link

RokuKent commented Feb 1, 2020

  • VSCode Version: 1.41.1
  • Local OS Version:10.14.6
  • Remote OS Version:4.4.0-ui19255.033-uiabi1-infong-amd64
  • Remote Extension/Connection Type: SSH/Docker/WSL
    SSH

Steps to Reproduce:

  1. Set up SSH connection based on working ssh connection from Mac client to remote device
    2.Connect

Does this issue occur when you try this locally?: No
Does this issue occur when you try this locally and all extensions are disabled?: No

Using ssh auto-logs into device. With Remote-SSH I'm getting:

[14:15:31.527] > Checking server status on port 36197 with wget
> fd507bdab9da: start
> sshAuthSock====
> agentPort==36197==
> webViewServerPort====
> osReleaseId==debian==
> arch==x86_64==
> webUiAccessToken====
> fd507bdab9da: end
[14:15:31.527] Received install output: 
sshAuthSock====
agentPort==36197==
webViewServerPort====
osReleaseId==debian==
arch==x86_64==
webUiAccessToken====

[14:15:31.529] Remote server is listening on port 36197
[14:15:31.529] Parsed server configuration: {"agentPort":36197,"osReleaseId":"debian","arch":"x86_64","webUiAccessToken":"","sshAuthSock":""}
[14:15:31.531] Starting forwarding server. localPort 61669 -> socksPort 61666 -> remotePort 36197
[14:15:31.531] Forwarding server listening on 61669
[14:15:31.531] Waiting for ssh tunnel to be ready
[14:15:31.532] Tunneled remote port 36197 to local port 61669
[14:15:31.532] Resolved "ssh-remote+home92371126.1and1-data.host" to "127.0.0.1:61669"
[14:15:31.535] ------
4:15:31.536] [Forwarding server 61669] Got connection 0
[14:15:31.547] [Forwarding server 61669] Got connection 1
[14:15:31.548] [Forwarding server 61669] Got connection 2
[14:15:31.590] Failed to set up socket for dynamic port forward to remote port 36197: Socket closed. Is the remote port correct?
[14:15:31.595] Failed to set up socket for dynamic port forward to remote port 36197: Socket closed. Is the remote port correct?
[14:15:31.595] Failed to set up socket for dynamic port forward to remote port 36197: Socket closed. Is the remote port correct?
[14:15:31.595] > channel 3: open failed: administratively prohibited: open failed
> channel 4: open failed: administratively prohibited: open failed
> channel 5: open failed: administratively prohibited: open failed

Does this plugin handle port 36197 as dynamic port forward? This could be ISP specific (1and1). Note that ssh from command line handles it.

@roblourens
Copy link
Member

administratively prohibited

Is tcp port forwarding allowed by your ssh server? This error often implies that it is disabled.

@RokuKent
Copy link
Author

RokuKent commented Feb 3, 2020

I need to open a ticket with the 1and1 admin, meanwhile is there a way to disable port forwarding so the connection behaves like the working ssh connection from the same device/terminal?

@roblourens
Copy link
Member

No, port forwarding is the only way we have to connect to our remote VS Code Server. Have this issue but no plans to address it: #92

@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants