Running tailscale up generates a valid loginURL in the client logs but does not display the loginURL to the console
#12119
Labels
Comments
bradfitz
added a commit
that referenced
this issue
May 13, 2024
The previous LocalBackend & CLI 'up' changes improved some stuff, but might've been too aggressive in some edge cases. This simplifies the authURL vs authURLSticky distinction and removes the interact field, which seemed to just just be about duplicate URL suppression in IPN bus, back from when the IPN bus was a single client at a time. This moves that suppression to a different spot. Fixes #12119 Updates #12028 Updates #12042 Change-Id: I1f8800b1e82ccc1c8a0d7abba559e7404ddf41e4 Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com>
bradfitz
added a commit
that referenced
this issue
May 14, 2024
The previous LocalBackend & CLI 'up' changes improved some stuff, but might've been too aggressive in some edge cases. This simplifies the authURL vs authURLSticky distinction and removes the interact field, which seemed to just just be about duplicate URL suppression in IPN bus, back from when the IPN bus was a single client at a time. This moves that suppression to a different spot. Fixes #12119 Updates #12028 Updates #12042 Change-Id: I1f8800b1e82ccc1c8a0d7abba559e7404ddf41e4 Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com>
bradfitz
added a commit
that referenced
this issue
May 14, 2024
The previous LocalBackend & CLI 'up' changes improved some stuff, but might've been too aggressive in some edge cases. This simplifies the authURL vs authURLSticky distinction and removes the interact field, which seemed to just just be about duplicate URL suppression in IPN bus, back from when the IPN bus was a single client at a time. This moves that suppression to a different spot. Fixes #12119 Updates #12028 Updates #12042 Change-Id: I1f8800b1e82ccc1c8a0d7abba559e7404ddf41e4 Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com> (cherry picked from commit 8aa5c35)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the issue?
After updating to 1.66.x, a customer (original ticket) has observed that running
tailscale upwhen the machine needs to be authenticated seems to hang from the user perspective. The client logs contain a valid loginURL that can be used to authenticate the device, however that URL is not printed to the console as expected after updating to 1.66.Steps to reproduce
tailscale up-> and see no output.Are there any recent changes that introduced the issue?
Upgraded client from 1.64 to 1.66
OS
Linux
OS version
Ubuntu 22.04
Tailscale version
1.66 & 1.66.1
Other software
No response
Bug report
BUG-8d8ee7e123451e7ad2e64e9f94d50be2d156c4ca8f59c0637aae6951727c470c-20240509160340Z-b0e65ad37fc32548
The text was updated successfully, but these errors were encountered: