Tailscale in Elk: "Tailscale Services is now in beta! This n..."

Tailscale Services is now in beta! This new feature makes hosting and scaling internal applications simpler and more secure than ever.

Blog: https://tailscale.com/blog/services-beta
Video: https://www.youtube.com/watch?v=mELAg50ljSA

Sign up for our webinar to learn more about Tailscale Services and other Fall Update Week features: https://tailscale.com/events-webinars/tailscale-fall-update?utm_source=Mastodon&utm_medium=owned-social&utm_campaign=fall-update-2025

October 28, 2025 at 1:03:58 PM

awesome, so I should be able to replace the caddy-tailscale plugin I've been using as a workaround to run multiple services on a single host with tailscale services right? And it's more general as it's not limited to http.

I think I'm holding it wrong, because when I set up a newly tagged node for running services I get "Partially configured: active" in the status line but no inkling of what I need to do to fully configure it.

Same. I’ve been banging my head against the wall and I can’t figure out what I’m supposed to change here. I keep getting “Partially configured: has-config, active”, when I should be able to approve the host to broadcast the service. I’m running Pi-hole in Docker on a Linux VPS and trying to serve the Pi-hole admin panel as a Tailscale service. I’ve been using TSDProxy for this purpose before this announcement.

Good to know that it's not just me! Hopefully we can get some guidance from

on why or what to do next.

I figured out what was the issue for me. I had the port configured wrong. I thought I had to put the port the application is listening on when creating a service in the admin console (in the case of my Docker container it’s port 8080). I was wrong.

If the command I’m using on the host is “tailscale serve --service=svc:pihole --https=443 localhost:8080”, what needs to be entered in the admin console is port 443, not 8080.