Forum

Hello, I have checked the status of your Wonder Mesh device "Tano内网".

What we see on our end:

"Tano内网" is a device connected via Wonder Mesh, linked to Zeabur through a mesh tunnel (Tailscale). According to our monitoring, this device has been repeatedly disconnecting and reconnecting over the past day, rather than just a single outage:

• 6/2 approx. 18:15 Disconnected → 22:45 Reconnected (CST)
• 6/3 approx. 10:25 Disconnected → 16:00 Reconnected
• 6/3 17:34 Disconnected again, currently still offline

When you posted (6/3 approx. 14:40), it fell right into the second outage period, which explains why you experienced "home network is back, but Zeabur still can't connect"—the local network was restored, but the mesh tunnel had not yet reconnected.

Such intermittent disconnections are usually caused by the device's network or the device itself (unstable home/NAT network, device entering sleep mode, Tailscale repeatedly reconnecting). Please troubleshoot on this device in order:

1. Ensure the device is powered on, has a stable network, and will not automatically enter sleep/hibernation (laptop lid closure and power-saving settings are the most common causes of such intermittent disconnections).
2. Check the Tailscale connection status:

tailscale status

• Linux: If it shows as stopped or stuck, restart it:

sudo systemctl restart tailscaled

• macOS: Wonder Mesh runs in a Lima virtual machine, first confirm it is running:

limactl list

3. If the above are normal but it still won't connect, uninstall and reinstall (after uninstallation, go back to the server page in the console, copy and execute the installation command to rejoin):

• Linux:

curl -fsSL https://cdn.zeabur.com/wonder/mesh-server-uninstall-linux.sh | sudo bash

• macOS:

curl -fsSL https://cdn.zeabur.com/wonder/mesh-server-uninstall-darwin.sh | bash

⚠️ For macOS, do not use sudo; the script must be executed as a regular user.

Related documentation:

• Troubleshooting / Restarting Tailscale: https://zeabur.com/docs/zh-CN/wonder-mesh/get-started
• Uninstallation instructions: https://zeabur.com/docs/zh-CN/wonder-mesh/uninstall

Please let us know if this device is Linux or macOS, whether it usually enters sleep mode, and if it recovers after restarting Tailscale/reinstalling, so we can continue to follow up.

It's Linux, Ubuntu LTS 24 server. I suspect it's an issue with my upstream OpenWrt configuration, so I will investigate further. Also, besides UDP and TCP, does Tailscale use other protocols like QUIC?

Understood, it's Ubuntu 24 LTS Server. If you suspect an issue with the upstream OpenWrt configuration, you should focus on checking the firewall/NAT rules to ensure they allow UDP (especially UDP 41641 used by WireGuard) and TCP 443 (for DERP relay fallback).

Regarding the protocols used by Tailscale, the detailed documentation for the installation script covers this. You can refer to it here: https://zeabur.com/docs/zh-CN/wonder-mesh/install-script-details

If you need any assistance from our side during the troubleshooting process (such as checking connection status, logs, etc.), feel free to reply at any time.

Confirmed, the UDP issue was caused by my OpenWrt configuration. I am fixing it myself, thanks.

The network issue has been resolved, but reconfiguring the node has caused the old node to interfere with the new one, preventing connection. The old node is 100.64.2.227, and the current node is 100.64.2.228.

=== Zeabur Mesh Server Setup Complete === Mesh IP: 100.64.2.228 tano@tano:~$ sudo tailscale ip 100.64.2.228 fd7a:115c:a1e0::2e5

The following error keeps appearing in the client logs:

magicsock: derp-7 does not know about peer, removing route

And the offline node is still visible in tailscale status.

Please help confirm:

1. Are there any residual old node records?
2. Is it safe to delete the old node 100.64.2.227?
3. Is it necessary to refresh the Headscale NetMap or node cache?

Thanks.

The latest error is: Jun 03 15:38:18 tano tailscaled[719]: Received error: PollNetMap: initial MapResponse lacked node

We have confirmed the following on our end:

1. There are indeed remnants from the old node. The control plane currently only sees the record for the earliest registered node. Although your new node (100.64.2.228) has been authenticated (machineAuthorized=true), it was not correctly added to the NetMap, which is why the PollNetMap: initial MapResponse lacked Node error is occurring.
2. This needs to be handled on the control plane side. This cannot be resolved from the device side. We have escalated this to the engineering team for confirmation and will update you on the progress as soon as possible.

I have confirmed with the engineering team that your issue is caused by a synchronization mismatch between the client and the control plane. You need to clear both sides to resolve it. Please follow these steps:

1. Run the uninstall script on your device:

curl -fsSL https://cdn.zeabur.com/wonder/mesh-server-uninstall-linux.sh | sudo bash

2. Delete this mesh server in the Zeabur console.
3. Create a new mesh server in the console, then copy and execute the new installation command on your device.

This will clear the old node records on both the client and the control plane, ensuring that re-registration won't conflict with any residual state.

Uninstall documentation: https://zeabur.com/docs/zh-CN/wonder-mesh/uninstall

Okay, sounds good.