You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
SSH
Steps to Reproduce:
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:
Does this plugin handle port 36197 as dynamic port forward? This could be ISP specific (1and1). Note that ssh from command line handles it.
The text was updated successfully, but these errors were encountered: