On Unraid 7.3.1 version with tailscale plugin version 2026.05.24.1252, was getting API not responding - nginx errors. The errors were being caused tailscale plugin. Once removed, no more nginx errors. Any suggestions please?

https://product.unraid.net/p/7-3-1-webgui-api-offline-after-reboot-array-shows-stopped-offline

23 hours ago, snailtrails said:

On Unraid 7.3.1 version with tailscale plugin version 2026.05.24.1252, was getting API not responding - nginx errors. The errors were being caused tailscale plugin. Once removed, no more nginx errors. Any suggestions please?

https://product.unraid.net/p/7-3-1-webgui-api-offline-after-reboot-array-shows-stopped-offline

I have it running on 7.3.1 on my production and multiple test servers. I’ll need more details/diagnostics to be able to understand what’s happening.

@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  ← present

On 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 indefinitely

Requested fixes:

1. 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.

2. Add a reload_services call in daily.php after tailscale cert completes, matching the behavior of tailscale-watcher.php on startup.

I am having a heck of a time with tailscale. I am only a few days into unraid, but a month into ugreen before their update wiped out my setup and got me here. The change is great, but I am so lost. I am installed on my NVME boot/cache, and at first I had a TS not ready messages. I moved the TS files from boot to the NVME, I can't get the TS IP's to connect local or remotely. I wiped it, used a docker install. It is the same. Any help is appreciated. I don't think I have made any changes that should affect this. I only have immich, jellyfin type apps, and have not messed with ports or anything wild. I can get everything working, but the IP connection and they are pingable, just not reachable. hours and hours into trouble shooting circles.

Thanks for any efforts.