Skip to content

Update Tailscale 1.90.9 -> 1.102.2 - #138

Merged
mikeodr merged 6 commits into
tailscale:mainfrom
nathanwasson:tailscale-update
Aug 26, 2026
Merged

mikeodr merged 6 commits into
tailscale:mainfrom
nathanwasson:tailscale-update

Conversation

@nathanwasson

Copy link
Copy Markdown
Contributor

Update Tailscale to address vulnerability as noted in #137

@nathanwasson

Copy link
Copy Markdown
Contributor Author

I created this PR hastily to get the ball rolling in case others want to help contribute as well. I'll build the container image tomorrow when I have time and test it to make sure the version update doesn't break functionality.

Signed-off-by: nathanwasson <126016071+nathanwasson@users.noreply.github.com>
Signed-off-by: nathanwasson <126016071+nathanwasson@users.noreply.github.com>
Signed-off-by: nathanwasson <126016071+nathanwasson@users.noreply.github.com>
Signed-off-by: nathanwasson <126016071+nathanwasson@users.noreply.github.com>
Signed-off-by: nathanwasson <126016071+nathanwasson@users.noreply.github.com>
Signed-off-by: nathanwasson <126016071+nathanwasson@users.noreply.github.com>
@nathanwasson

Copy link
Copy Markdown
Contributor Author

Alright, had to make some additional commits to make the image build and the linter happy, but here it is for testing: https://github.com/nathanwasson/caddy-tailscale/pkgs/container/caddy-tailscale

@nathanwasson

Copy link
Copy Markdown
Contributor Author

I deployed my updated image to my dev environment, and both the container and my applications exposed via caddy-tailscsale all seem to be happy.

Here you can see in the Tailscale admin panel on top the current official caddy-tailscale image running with the outdated version of Tailscale and on the bottom is my updated caddy-tailscale image running with the current version of Tailscale.

image

@nathanwasson nathanwasson changed the title Update Tailscale 1.90.9 -> 1.102.1 Update Tailscale 1.90.9 -> 1.102.2 Aug 5, 2026
@nathanwasson

Copy link
Copy Markdown
Contributor Author

I think I've done my part here, but I'm happy to help out however else may be needed. @willnorris would you be able to review this version update to address the known security vulnerability in the version of Tailscale shipped with the current release of caddy-tailscale?

@itsjxck

itsjxck commented Aug 5, 2026 •

Copy link
Copy Markdown

@nathanwasson I've been trying this out, and it seemingly worked the first time I ran it, but now I'm getting errors like this for every request:

{"level":"error","ts":1785937465.922693,"logger":"tls.handshake","msg":"external certificate manager","remote_ip":"100.106.36.24","remote_port":"64038","sni":"<site-name>.<ts-domain>.ts.net","cert_manager":"caddytls.Tailscale","cert_manager_idx":0,"error":"Get \"http://local-tailscaled.sock/localapi/v0/cert/<site-name>.<ts-domain>.ts.net?type=pair\": Get \"http://local-tailscaled.sock/localapi/v0/cert/<site-name>.<ts-domain>.ts.net?type=pair\": context deadline exceeded"}

I have 4 sites configured in my caddyfile, all specified like this:

https://<site-name>.<ts-domain>.ts.net {
	bind tailscale/<site-name>
	...
}

I can see that each site is connected as a tailscale machine, they are all online, and they are all reachable with tailscale ping. It looks like traffic is routed to Caddy correctly, but then theres something up with Caddy's ability to pull the certs from Tailscale. Has this version update changed the way the certs should be pulled from Tailscale?

Update: I just tried the other sites that are configured, and they work fine. 3 of 4 work and I have no context on why the 1 doesn't. Will keep digging

Update 2: I changed the name of the site and now everything works, how bizarre

@mikeodr
mikeodr merged commit de41b24 into tailscale:main Aug 26, 2026
4 checks passed
chrishoage added a commit to chrishoage/caddy-tailscale that referenced this pull request Oct 25, 2026
* upstream/main:
  Update Tailscale 1.90.9 -> 1.102.2 (tailscale#138)

# Conflicts:
#	go.mod
#	go.sum
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants