From 29e18d80b4f03bfee6edfa6b2a34632d29595847 Mon Sep 17 00:00:00 2001 From: Kristoffer Dalby Date: Wed, 30 Sep 2026 16:40:22 +0000 Subject: [PATCH] docs: note the audit-log shutdown lasts until tailscale up Clients that opt out of logging themselves hit it whatever logtail.enabled says. --- docs/about/faq.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/about/faq.md b/docs/about/faq.md index c6bb8cb7e..101112337 100644 --- a/docs/about/faq.md +++ b/docs/about/faq.md @@ -208,7 +208,8 @@ applied by a client once it successfully connected with Headscale. See the confi Do not grant the `https://tailscale.com/cap/data-plane-audit-logs` node attribute while `logtail.enabled` is `false`. A client with log submission disabled treats this attribute as "the tailnet requires logging" and turns itself off, as -`tailscale down` would. +`tailscale down` would. It stays off until the attribute is removed and `tailscale up` is run. A client started with +`TS_NO_LOGS_NO_SUPPORT=true` or `--no-logs-no-support` reacts the same way, whatever `logtail.enabled` says. Alternatively, logging can also be disabled on the client side. This is independent of Headscale and opting out of client logging disables log submission early during client startup. The configuration is operating system specific and