NordVPN Meshnet Not Working
Workaround available Windows, macOS, Linux, iOS, Android Updated October 21, 2026
Quick answer
Meshnet failures usually come from a device that is asleep or suspended (iOS), duplicate machine IDs on cloned Linux systems, or leftover keychain entries on macOS. Keep the remote device awake, give each device a unique identity and reset Meshnet.
Most likely fix: Keep the remote device awake (iOS).
Symptoms
Meshnet won't turn on, the toggle spins forever, a device shows as active but can't be reached, or two devices show the same Meshnet name/IP.
Why it happens
- iOS suspends the app when the device is locked, so it appears online but can't send or receive
- Linux machines cloned or restored from backup share machine-id and hostname
- Leftover Keychain entries after reinstall on macOS
- Outdated app version
How to fix it
Try these in order — the most common fix is first.
1. Keep the remote device awake (iOS)
- Keep the iPhone or iPad unlocked with the app open while you need to reach it
- Use an always-on computer as the Meshnet host instead; NordVPN says it can't work around iOS suspension
2. Fix duplicate identities on Linux
- Change the hostname on one of the cloned machines
- Do not edit the machine-id file manually
- Restart the NordVPN daemon and turn Meshnet on again
3. Clean the Keychain and reinstall (macOS)
- Quit NordVPN
- Open Keychain Access and delete leftover NordVPN entries
- Relaunch NordVPN and enable Meshnet; each device should get a unique Meshnet IP and Nord name
4. Update and report
- Update the app on every device
- If it still fails, send support your OS, app version, error message and reproduction steps
This guide also covers
- nordvpn meshnet not working
- meshnet not connecting
- nordvpn meshnet linux connection failed
- nordvpn meshnet discontinued
Still not working?
If NordVPN keeps failing, you're not alone. See every NordVPN problem users report or the alternatives people switch to.