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.

I have been running the Tailscale plugin alongside Nginx Proxy Manager (NPM) for a year. However, since a few weeks these conflict with eachother.

When trying to start the NPM docker I now get an error saying:

docker: Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint NginxProxyManager (d9ecadce4b2c6c3d7a2561817a1b4303fa2bb679edbcd4db924629c4618916a2): failed to bind host port 0.0.0.0:443/tcp: address already in use

This 443 port is used by Tailscale. When I deinstall the Tailscale plugin, the NPM docker is starting correctly.

What has changed and how to fix this?

Edited July 7Jul 7 by monsieurrouge

I cannot install tailscale

I get this Network failure error

any idea how to fix it?

thanks

Downloading plugin
plugin: installing: tailscale.plg
Executing hook script: CA_preHook
Clearing Community Applications plugin cache
Executing hook script: pre_plugin_checks


plugin: downloading: unraid-tailscale-utils-2026.08.06.0154-noarch-1.txz ...
plugin: unraid-tailscale-utils-2026.08.06.0154-noarch-1.txz download failure: Network failure
Executing hook script: CA_postHook
Clearing Community Applications plugin cache
Executing hook script: post_plugin_checks
Plugin installed

19 hours ago, DuckWaze said:

Hello,

I have a strange issue with my Tailscale plugin on Unraid. After updating yesterday to the newest Unraid version (7.3.2) Not sure of the update have anything to do with it, but just F.Y.I. and updating the plugins, I can no longer reach the Unraid web interface via its Tailscale IP. Locally, everything works fine — the issue is only when trying to access it remotely through Tailscale.

What I have checked:

• The Tailscale node "Unraid" is online and pingable.

• I can ping from the Unraid server (via Tailscale) to my notebook.

• From the Tailscale admin console, I can ping all devices.

• Restarting Tailscale on the server — no effect.

• Deleting Tailscale on the server and reinstalling — no effect.

• Full reset of the Tailscale plugin and re-authenticating — no effect.

A second strange issue is that all my dockers that are exposed (Wordpress, WikiJS, Ect) also don't work. Not related to this topic but just F.Y.I

I am using Cloudflare, Gandhi & Bunny.net for different domains, checked the WAN on al of those and there a correct neither one docker is external working by domain name.

My immich docker is only accable by tialscale IP of the unraid server, again i can ping the tailscale IP from the phone, but Immich cant reach the IP.

I check the router and did even a factory reset, with no effect.

Any help would be appreciated!

unraid-diagnostics-20260806-2023.zip

The Tailscale plugin webui works normal or not? can other device reached to the unraid machine?

8 hours ago, trevor.ostrander said:

I cannot install tailscale

I get this Network failure error

any idea how to fix it?

thanks

Downloading plugin
plugin: installing: tailscale.plg
Executing hook script: CA_preHook
Clearing Community Applications plugin cache
Executing hook script: pre_plugin_checks


plugin: downloading: unraid-tailscale-utils-2026.08.06.0154-noarch-1.txz ...
plugin: unraid-tailscale-utils-2026.08.06.0154-noarch-1.txz download failure: Network failure
Executing hook script: CA_postHook
Clearing Community Applications plugin cache
Executing hook script: post_plugin_checks
Plugin installed

Have you checked your network to GitHub?

1 hour ago, Chengnan said:

Have you checked your network to GitHub?

It was a network issue but I don't understand how because everything else works fine. I only discovered it when I tried to ping GitHub.com. couldn't ping anything else such as google.com either. I've somehow lost dns query ability on unraid. I fixed it with manually setting the dns server to something public (9.9.9.9). My router is OpenWRT and it works on every other device in the house. Its internal IP is 10.1.1.1.

cat /etc/resolv.conf gave this when set to my router

# Generated by dhcpcd from br0.dhcp

domain lan

nameserver 10.1.1.1

nslookup even appears to work but when I try to ping it fails

nslookup google.ca

Server: 10.1.1.1

Address: 10.1.1.1#53

Non-authoritative answer:

Name: google.ca

Address: 142.250.73.131

Name: google.ca

Address: 2607:f8b0:400a:800::2003

cat /etc/resolv.conf after manual setting dns and pings are successful

# Generated by rc.inet1

nameserver 9.9.9.9  # eth0:v4

The problem only showed up here. I've updated docker apps and even unraid itself while it was in this state so it clearly has connection to the internet. Just not for installing plugins and manual commands line pings.

it's working for now but it shouldn't be like this

I found this old thread with similar issue https://forums.unraid.net/topic/123158-random-loss-of-dns/page/2/

they appeared to resolve it by replacing the router. I don't really want to start messing with my router since it's working flawlessly with all other devices.

any additional thoughts?

Edited August 7Aug 7 by trevor.ostrander