New issue
Advanced search Search tips

Issue 860039 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 9
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Unable to SSH to remote computer

Project Member Reported by ckingsley@google.com, Jul 3

Issue description

Chrome Version       : Version 67.0.3396.99 (Official Build) (64-bit)
URLs (if applicable) :  chrome-extension://pnhechapfaindjhompbnflcldabbghjo/html/nassh.html#profile-id:78a0
Other browsers tested: None
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari:
    Firefox:
       Edge:

What steps will reproduce the problem?
(1) Follow steps 1-4 here:  http://shortn/_TcckU1zYU7
(2) Then follow steps 1-4 here:  http://shortn/_uaz3K5JayE
(3)

What is the expected result?  Steps 5-6 here:  https://support.google.com/techstop/answer/2675787

What happens instead?  It is stuck here:  

Looking up relay server using: sup-ssh-relay.corp.google.com:443
Found relay server: https://sup-ssh-relay.corp.google.com:443/
Connecting to ckingsley@gideon.c.googlers.com...
Loading NaCl plugin... done.


Please provide any additional information below. Attach a screenshot if
possible.

I am working from home but never had any issues before.  See associated bug here:  https://b.corp.google.com/issues/111111526

 
Labels: Needs-Triage-M67
Cc: rbasuvula@chromium.org
Labels: TE-NeedsTriageHelp
This looks like SSH related issue and not having the permission to test in-House TE, hence adding the respective label for it to triage further.

Thank You!
if it was working before but stopped, you should check with techstop and file some b/ tickets for cloudtop peeps.  the Secure Shell client hasn't changed, and based on the output you've shown, the client is waiting for the relays and/or servers to respond.
This is fixed:

Fixed on GUTS ticket http://m.guts.corp.google.com/?ticket=33717846.   go/crd-auth tool which is giving bad OAuth tokens.  I had to 1) reboot my Cloudtop 2) open go/crd-auth in an incognito window and 3) set up CRD from there.
Status: WontFix (was: Unconfirmed)

Sign in to add a comment