Skip to content

CLI Login not working with custom proxy port after upgrade to 3.1.1 #2458

Open

Description

What happened:

tsh login --proxy=domain:443

error timeout trying to connect to port 3080 instead of 443

What you expected to happen:

be able to login

How to reproduce it (as minimally and precisely as possible):

tsh login --proxy=domain:443

Environment:

  • Teleport version (use teleport version): 3.1.1
  • Tsh version (use tsh version): 3.1.1

Relevant Debug Logs If Applicable

INFO [CLIENT] no host login given. defaulting to client/api.go:700
INFO [CLIENT] [KEY AGENT] Connected to the system agent: "/run/user/1000/keyring/ssh" client/api.go:1907
DEBU [CLIENT] not using loopback pool for remote proxy addr: domain:443 client/api.go:1868
DEBU [CLIENT] HTTPS client init(proxyAddr=domain:443, insecure=false) client/weblogin.go:531
DEBU [CLIENT] not using loopback pool for remote proxy addr: domain:3080 client/api.go:1868

Enter password for Teleport user user_name:
Enter your OTP token:

DEBU [CLIENT] HTTPS client init(proxyAddr=domain:3080, insecure=false) client/weblogin.go:531

ERROR REPORT:
Original Error: *trace.ConnectionProblemError dial tcp ip:3080: i/o timeout

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

bugtshtsh - Teleport's command line tool for logging into nodes running Teleport.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions