Skip to main content

Emergency Troubleshooting Instructions

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​

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.

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.