tailscale/tailscale

cmd/tailscale: timeout hitting LetsEncrypt to get cert isn't surfaced well in errors

Open

#14677 opened on Jan 17, 2025

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Go (31,565 stars) (2,554 forks)batch import
buggood first issueneeds-fix

Description

What is the issue?

Image

i can reach DERP server, but can't get my cert.

Image

Steps to reproduce

I don't know what's wrong with my device,sorry i searched but no any information about this

And i test subnet of this router's linux device to get cert by itself.it is worked.

Are there any recent changes that introduced the issue?

No response

OS

linux openwrt

OS version

openwrt 24

Tailscale version

1.66.4-1 (OpenWrt)

Other software

It is running a adguardhome on this router,but magicDNS is working. I think there are no error about this.

Bug report

No response

Contributor guide

Tech stack
go
Domain
clibackend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Go programming languageunderstanding of HTTPS/TLS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the cert acquisition flow in cmd/tailscale. Look for where the HTTP request to LetsEncrypt is made and how errors are handled. The issue suggests that timeout errors are not surfaced properly. Check error wrapping and logging near the cert fetch function. Also review any existing comments or linked issues for context.