Troubleshooting and FAQ

A device shows offline

1. On the device, run tailscale status. If it says the client is stopped or logged out, start it (sudo tailscale up) or, if it was logged out, add the device again with a new key.
2. Check that the device has internet at all.
3. On Linux, restart the client: sudo systemctl restart tailscaled.
4. After a change of network (Wi-Fi to mobile data, a new router) a device may need a minute to come back.

On a private network's page the status refreshes by itself every 10 seconds; on the public network page, reload the page to see the current status.

I can't reach another device

• Both devices must be online and in the same network.
• Public network: devices of other accounts are reachable only through a room where both devices are ticked.
• Private network: the access rules must allow it — use Check access with the device, port and protocol.
• Use the 100.x address or the device's name; the device's LAN address works only through a subnet router.
• The service must listen on the Tailscale address or on all addresses, not only on 127.0.0.1.
• The device's own firewall must let the connection in. Windows, for example, blocks incoming ping and most ports by default.
• tailscale ping 100.64.0.7 shows whether the devices see each other at the network level, and whether the path is direct or through a relay.

A subnet behind a router doesn't answer

1. The router advertises the subnet, and the route is approved on its page.
2. On Linux the router has IP forwarding on.
3. The device you connect from accepts routes — on Linux it's off by default.
4. The access rules allow the subnet: Check access with the subnet as the destination tells it, and warns if the route isn't approved.
5. If two LANs use the same subnet, ordinary routes can't work — use sites.

A router lost access to its own LAN

The router was started with --accept-routes and now sends its own LAN into the tunnel. On the router:

sudo tailscale set --accept-routes=false

If the device must accept routes for other subnets, keep its own LAN direct instead: sudo ip rule add to 192.168.1.0/24 priority 2500 lookup main.

The join key doesn't work

• A key works once. In a private network it also expires in 1 hour, in the public network in 7 days. Create a new one with Add device.
• The --login-server in the command must be the address of the network the key is from.
• A device that was in another network needs --force-reauth added to the command.
• In the public network, the key isn't issued when the device limit is reached.

“Network unavailable”

The network's server didn't answer the dashboard; the message says why (an error code or no response). The devices usually keep talking to each other in the meantime. Refresh the page in a minute; if it lasts, write to support with the network's name.

Access rules aren't applied yet

The rules are saved, but the network's server hasn't taken them yet. mesh-net retries automatically; Retry now on the rules page tries at once. See the details.

A name still points to the old address

• Resolvers keep an answer for its TTL (300 seconds for names in our zones) — wait a few minutes, or check with dig +short from another network.
• A record with the status pending didn't reach DNS — save it again.
• For DDNS, see If DDNS doesn't work; for your own domain — that its name servers point to mesh-net.

The email with the code doesn't come

• Look in the spam folder, and wait a minute or two.
• Request the code again on the same page. A new code replaces the previous one at once, so enter the code from the latest email. A code stops working after 10 minutes or 5 wrong tries.
• Check the email address you typed.
• Once you're in, send a test email and add our address to your contacts.

I was signed out

After 30 minutes without activity the dashboard signs you out — see Automatic sign-out. Sign in again; nothing is lost.

Frequently asked questions

Is the public network really free?

Yes, on every plan: up to 5 devices and 3 rooms. More devices — with the add-on, more rooms — with the Paid plan.

Does my traffic go through mesh-net?

No. Devices connect to each other directly; the coordination server only introduces them. When a direct path is impossible, the traffic goes through a relay, encrypted end to end — the relay can't read it. The exception is published services: their visitors come through our server by design.

Which apps do I need?

The standard Tailscale client for your OS — mesh-net networks are headscale networks. The steps for every OS: public network, private network.

Can I take my network and leave?

Yes: export it and move it to your own headscale with the same addresses and keys — see Export, import, backup and restore.

How do I delete my account?

Write to support from the account's email. A Free account that isn't used is also deleted automatically, after a warning — see Inactive free accounts.

Contact support

1. Open Support in the menu and press New ticket.
2. Fill in the Subject and the Message and press Send ticket.
3. The answer comes to the ticket's page and by email. Reply on the same page; a closed ticket can't be reopened — open a new one.

You can also write to support@mesh-net.space. It helps to mention the network and device names, what you did, the exact message on the page and when it happened.