Troubleshooting
Ping is not working
First, make sure your device is authorized on the network and you're using the ZeroTier assigned Managed IP address. Aside from that, some OSes block pings in their local firewall by default.
Windows Firewall
ZeroTier versions 1.10.3 and greater automatically enable ping on ZeroTier adapters.
macOS Firewall
The firewall is not enabled by default on macOS, and thus pings will not be blocked by default. If your firewall is enabled on macOS, go into System Preferences -> Security & Privacy. Under Firewall Options, ensure "Enable stealth mode" is disabled. Stealth mode blocks pings.
Linux Firewalls
There are far too many Linux distributions out there to list instructions for all of them here. Please refer to your distribution's documentation for how to unblock ICMP packets.
Click here to create your network and start adding devices.
Error: Cannot connect to ZeroTier service (or Node ID "Unknown" in the GUI apps)
This error means that the ZeroTier background service on your computer is either not running, or your local firewall is preventing the UI or CLI from talking to it.
Windows Service
Open Task Manager and go to the "Services" tab. Scroll down until you see "ZeroTierOneService". The status column should say "Running". If it does not, right click on the line and click "Start"
macOS Service
Open Terminal.app and execute the following commands
sudo launchctl unload /Library/LaunchDaemons/com.zerotier.one.plist
sudo launchctl load /Library/LaunchDaemons/com.zerotier.one.plist
Linux Service
If your Linux distribution uses systemd, execute:
sudo service zerotier-one start
If not, execute:
/etc/init.d/zerotier-one start
Still doesn't work?
Your system firewall is likely blocking communication with the ZeroTier service. Look up instructions for how to unblock an application from the firewall for your OS. ZeroTier will need to be accessible via TCP port 9993 for the UI and CLI to interact with it.
Emergency Instructions
"It was working, but now it's not and I'm not sure why. And I need to get up and running quick."
First, check with your friendly firewall admin that no configuration in the physical network connection has changed.
See the CLI article for help with the CLI.
We're not aware of any bugs that require these steps, or we'd fix them, but sometimes people try the below.
Listed in order of severity:
Restart the service
- macOS
- Windows
- Linux
Open Terminal.app, paste the below, and press enter:
sudo launchctl unload /Library/LaunchDaemons/com.zerotier.one.plist
sudo launchctl load /Library/LaunchDaemons/com.zerotier.one.plist
It will ask you for your password. It's the password you use to log in to your mac.
systemctl restart zerotier-one
- Type "Services" into the Start Menu to open the Windows Services Manager
- Start and Stop the zerotier-one service in the Windows Services Manager.
Leave all networks and rejoin them
Use the UI, or
zerotier-cli leave <network-id>
and zerotier-cli join <network-id>
Stop service, Delete peers.d, Start service
Find peers.d in the zerotier system directory
Reset Node ID
The new node ID will have be re-authorized on any networks, and the node's managed IP address manually re-assigned if needed.
-
Stop the service
-
Move or delete identity.secret and identity.public files in the zerotier system directory
-
Delete peers.d too
-
Start the service
Troubleshooting Connection Issues
It can be a little tricky to figure out why something isn't working. We'll try to improve this. Unfortunately you need to use the CLI to troubleshoot.
It's a peer to peer system, so we might need to check 2 or more nodes to deduce where the problem is.
Go through these steps and see corporate firewalls and Router Tips for more explanation.
Peers List
Check this command on both peers
zerotier-cli peers
If one device has many "RELAY" connections, it's having a hard time connecting to things.
If the connections to the PLANETs are RELAY, the node is having a very hard time. UDP traffic may be blocked.
Status
zerotier-cli info
it eventually says "RELAY" instead of "ONLINE" if UDP traffic is blocked.
Checking for Symmetric NAT
zerotier-cli info -j
Look at the "listeningOn" and "surfaceAddresses". If the surfaceAddress list large is constantly growing for each node you ping
, this node may be behind Symmetric NAT. Other devices will have a hard time connecting with it.
See corporate firewalls for more info on Symmetric NAT.
Ideally there is 1 surface address for each listening address/port.
For a simplified example, if your computer only has 1 network interface and IP address, listeningOn
will look like this:
"listeningOn": [
"192.168.100.193/9993",
"192.168.100.193/55957",
"192.168.100.193/30431"
]
then the surfaceAddresses
should have only 3 entries
"surfaceAddresses": [
"198.51.100.9/24/9993",
"198.51.100.9/30431",
"198.51.100.9/2785"
],
Usually there is more going on in these entries and it can be hard to read. The output of zerotier-cli dump
contains this information. If you send it to us, we can read it for you.