- Notifications
You must be signed in to change notification settings - Fork927
feat(agent): add http debug routes for magicsock#7287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
839ae15
to3138432
Compare9187327
toa3d2a9e
CompareThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Ship it!
mafredri left a comment• edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I think we should be careful about using up ports in user workspaces, but don't really have a suggestion for an improvement here. Maybe this debug endpoint could be enabled on-demand or something in future.
Yeah, I was thinking about that while writing this. I think users probably wouldn't be too stoked we're automatically taking up some commonly used ports. Another thing we could do is use some of our reserved ports in Wireguard, but then a user couldn't port-forward to them. |
Uh oh!
There was an error while loading.Please reload this page.
Exposes Tailscale's magicsock debug, which can be helpful when debugging connections.