Troubleshooting guide

Tailscale Synology Package Update: When Remote Requests Time Out After Updating

Category: Remote Access

You updated the Tailscale package on your Synology NAS, and now the package shows connected but every remote request times out. This points to a state mismatch after the update, not a total failure.

Confirm the package and tunnel state

Open Package Center and check the Tailscale version. Then SSH into the NAS and run sudo tailscale status. Look for your NAS as the first line and note whether it says active or idle. If it says idle despite the package showing connected, the tunnel is not passing traffic. Also run sudo tailscale netcheck and check the UDP line; if UDP is blocked, Tailscale may be falling back to a relay that the update did not re-register correctly.

Restart the tunnel cleanly

Stop the Tailscale package in Package Center, wait ten seconds, then start it again. Re-run sudo tailscale status and confirm the NAS line shows active. If it still shows idle, run sudo tailscale down followed by sudo tailscale up. Watch for any error about the node key or authentication; that means the update invalidated the stored state.

Verification test

From a remote device on your tailnet, ping the NAS Tailscale IP with ping -c 4 <nas-tailscale-ip>. A reply confirms the tunnel is passing traffic. Then open one shared folder over the tailnet. If ping succeeds but the share times out, the issue is service-level, not the tunnel.

Rollback note

If the tunnel stays idle after a clean restart, reinstall the previous Tailscale package version from Package Center’s version list, then run sudo tailscale up again. This restores the last known working state before the tailscale synology package update.

If these steps do not restore access,

A phone on cellular data opening a Synology share through Tailscale

Ask for help with your tailscale status output.


Back to the service page · Ask about this exact symptom