Open Valien opened 2 years ago
This might be related to https://github.com/gravitational/teleport/issues/26946
In modern times the error is a bit different, but we can still clean this up:
➜ tsh login --auth=github --proxy=example.com
If browser window does not open automatically, open it by clicking on the link:
http://127.0.0.1:61352/7ab38508-7545-4777-9e7d-0ad5a8503234
> ...
➜ tsh ssh ubuntu@
ERROR: failed connecting to host :0: failed to receive cluster details response
rpc error: code = Unknown desc = failed to dial target host
cannot route to empty target host
Expected behavior:
Not sure that Teleport is supposed to do this. It should probably return a friendly message due to the incomplete
tsh ssh
command being run but somehow is not capturing that and routing to a login screen instead.Current behavior:
Running a
tsh ssh <user>@
while logged into a Teleport cluster will generate a new login URL and open your default browser to authenticate in. It will then return back to the CLI with an error message (and updated certificate I think).Sequence of messages:
This is expected behaviour as we've not logged in or defined anything to login.
All is well.
Browser returns a successful login but then drops to this error. Teleport audit logs show a new cert being generated as well.
Bug details:
v10.3.1
client and servertsh login
via CLItsh ssh ubuntu@
and hit enter