Teleport: Change default port order to 443, 3080
Feature Request
tsh login --proxy=example.com by default tries 3080 and then 443. The problem is that most of the time 3080 is blocked,
and the above command will hang before trying next port 443. Why don't we switch the order of ports, with 443 being the default, and 3080 a fallback.
Motivation
This will improve UX for everyone
klizhentas
>All comments
Not sure if it would be possible, but using the Happy Eyeballs algorithm (https://tools.ietf.org/html/rfc8305), used for IPv4/IPv6, could give the best of both worlds. Basically, send a request on both 443 and 3080, and see which one comes back first (and is a valid teleport endpoint).
I was also bitten by the default 3080 thing, and switched from 443 just to make my developers' lives easier.
sskousen
on 20 Nov 2020
👍3
❤2
🚀1
Was this page helpful?
0 / 5 - 0 ratings
Related issues
webvictim
路
3Comments
binoue
路
3Comments
webvictim
路
4Comments
webvictim
路
6Comments
awly
路
5Comments
Most helpful comment
Not sure if it would be possible, but using the Happy Eyeballs algorithm (https://tools.ietf.org/html/rfc8305), used for IPv4/IPv6, could give the best of both worlds. Basically, send a request on both 443 and 3080, and see which one comes back first (and is a valid teleport endpoint).
I was also bitten by the default 3080 thing, and switched from 443 just to make my developers' lives easier.