Emergency Troubleshooting Instructions
Emergency Instructions
When ZeroTier stops working unexpectedly and you need to restore connectivity quickly, follow these troubleshooting steps in order of increasing severity.
Before proceeding: Verify with your network administrator that no firewall or network configuration changes have been made that might affect ZeroTier connectivity.
See the CLI documentation for detailed command-line interface instructions.
The following steps are listed in order of severity, starting with the least disruptive:
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
What is PORT_ERROR
A PORT_ERROR
can happen when the Virtual Network Port cannot be brought online for some reason. See specific instructions for resolving this on macOS.