ExcaliburVT

@EDACerton Longtime lurker, and I had reported this issue about 6 months ago and provided logs, but had not been able to narrow down the root cause. (I also wasn't using AI so much back then). Today I exported the diagnostic logs and asked Claude to analyze and this is what it came up with: Bug Report: Tailscale plugin breaks nginx daily due to stale MagicDNS hostname and missing reload_services call Environment: Unraid 7.2.5, Tailscale plugin (latest), tailscaled v1.98.3 Symptom: After a few minutes of working fine following a manual restart, Tailscale connections drop. The plugin must be manually restarted to restore access. This repeats every day around the same time. Root Cause (from log analysis): There are two bugs that combine to cause the failure: Bug 1 — Stale hostname in cert commands. My tailnet's MagicDNS suffix is [tailnet-name].ts.net, so my correct FQDN is [hostname].[tailnet-name].ts.net. However, both daily.php and tailscale-watcher.php are hardcoded to request certs for [hostname].magicdns.ts.net — the old-style MagicDNS format that no longer matches my tailnet. The cert command fails silently every morning. The plugin should derive the hostname dynamically from the live Tailscale state (which correctly reports the current DNS name) rather than using a cached/hardcoded value. Bug 2 — daily.php does not call reload_services after running tailscale cert. On startup, tailscale-watcher.php correctly calls reload_services after the cert command, which causes nginx to pick up the new cert and bind properly to the Tailscale IP. However, daily.php runs tailscale cert at ~4:41 AM every day and then exits without calling reload_services. This causes nginx to lose its listener on the Tailscale IP (100.x.x.x:80), after which the watcher enters an infinite nginx restart loop that never self-recovers. Evidence from logs (tailscale-utils.log): On startup (works): tailscale-watcher.php: exec: tailscale cert ... [hostname].magicdns.ts.net tailscale-watcher.php: exec: /usr/local/emhttp/webGui/scripts/reload_services ← presentOn daily timer (breaks): daily.php: exec: tailscale cert ... [hostname].magicdns.ts.net ← reload_services never called tailscale-watcher.php: WebGUI not listening on 100.x.x.x:80, terminating and restarting ← loops every 2 minutes indefinitelyRequested fixes: Derive the cert hostname dynamically from tailscale status or the local API rather than using a hardcoded/cached value, so it stays correct if the tailnet MagicDNS suffix changes. Add a reload_services call in daily.php after tailscale cert completes, matching the behavior of tailscale-watcher.php on startup.

I like the "The Tailscale key will expire" banner that was added. Any chance that the plugin will alert as that date gets close? If not can that be added? Basically the same process that is used for Unraid alerts like the plugins version update: Event: Plugin - tailscale [2025.11.05.0614] Subject: Notice [<servername>] - Version update 2025.11.05.0614 Description: A new version of tailscale is available Importance: normal

Yeah I'm still having this issue. Every time the server reboots Tailscale initially works, but then sometime in the first few minutes its "broken" and I have to connect directly via the local IP, go to the Plugin settings and restart it. I've uploaded a new diagnostic: 3a5d248fe0e88cc5191101032bcecbe7

@EDACerton uploaded

Uploaded: ID: e53c9939811253fb94ec764d070e1443

I'm having an issue where the Tailscale plugin doesn't seem to work after OS startup. I have to go to the Unraid admin page via direct IP and log in, then go to the Tailscale plugin settings page and restart it. After that I'm able to successfully access Unraid admin via Tailscale. This was not happening until recently, any idea what might be happening? I have attempted: 1) Uninstall and re-install the plugin 2) Re-authenticate As a side issue (which I assume is totally unrelated) I am seeing is that when I access the settings page I see this in the log. Looks like the static js and css files are missing from the plugin? ``` Aug 25 18:35:13 <servername> nginx: 2025/08/25 18:35:13 [error] 36898#36898: *2095 open() "/usr/local/emhttp/plugins/tailscale/vendor/select2/select2.min.js" failed (2: No such file or directory) while sending to client, client: 192.168.1.100, server: , request: "GET /plugins/tailscale/vendor/select2/select2.min.js HTTP/1.1", host: "192.168.1.103", referrer: "http://192.168.1.103/Settings/Tailscale" Aug 25 18:35:13 <servername> nginx: 2025/08/25 18:35:13 [error] 36898#36898: *2078 open() "/usr/local/emhttp/plugins/tailscale/vendor/select2/select2.min.css" failed (2: No such file or directory) while sending to client, client: 192.168.1.100, server: , request: "GET /plugins/tailscale/vendor/select2/select2.min.css HTTP/1.1", host: "192.168.1.103", referrer: "http://192.168.1.103/Settings/Tailscale" ```