Common issues on Linux
Learn how to effectively tackle Meshnet-related problems on Linux.
Introduction
This page offers actionable troubleshooting steps for resolving issues that may arise when using Meshnet on Linux machines.
Possible issues and their solutions
This section outlines various situations or problems you may encounter while using Meshnet. For each case, you'll find a technical explanation to help you understand the root cause, as well as troubleshooting methods to resolve the problem.
Duplicated Meshnet IP address
The NordVPN Linux app uses the content of two files for machine identification in Meshnet — machine-id and hostname. If a system is duplicated or installed from a backup, there is a high chance that the values for both systems will be the same, thus leading to identical Meshnet details.
The machine-id
file contains the unique machine ID, which is generated during system installation. It is not recommended that this file be manually altered. However, the hostname
file can be freely modified to allow distinction between the devices.
Cannot access Docker containers over Meshnet
In its current implementation, Meshnet treats the Docker IP range (172.17.0.0/16
subnet) as a local network. This means that with default permissions, if any network packets from peer devices are headed to this IP range, Meshnet will drop them to prevent unintended traffic from reaching LAN IP ranges.
Contact support
If you encounter a problem not described on this page or you cannot resolve a problem using the provided guidelines, feel free to contact the NordVPN support staff at support.nordvpn.com.It would be highly beneficial if you could provide the following information when reaching out:
Tip
You can find your current NordVPN app version using the nordvpn -v
command.
Last updated