Mac unable to connect to network (stuck REQUESTING_CONFIGURATION)

Mac Mini M1 (12.1 Monterey)

Unable to connect to network and device is stuck in REQUESTING_CONFIGURATION. Other devices on the same network (WIFI and same subnet) including an M1 Macbook Air are connecting and communicating fine. No firewall or firewall type software installed on the host. All clients are 1.8.4

zerotier-cli info
200 info 62caae64b9 1.8.4 ONLINE

zerotier-cli listnetworks
200 listnetworks <nwid> <name> <mac> <status> <type> <dev> <ZT assigned ips>
200 listnetworks {networkremoved}  de:2b:72:3e:e7:8a REQUESTING_CONFIGURATION PRIVATE feth2403 -
sudo zerotier-cli peers
200 peers
<ztaddr>   <ver>  <role> <lat> <link> <lastTX> <lastRX> <path>
61d294b9cb -      PLANET    71 DIRECT 8479     3335
62f865ae71 -      PLANET   227 DIRECT -1       3181
778cde7190 -      PLANET    53 DIRECT 18       3355
992fcf1db7 -      PLANET   126 DIRECT -1       3282

Have done this several times:

sudo launchctl unload /Library/LaunchDaemons/ 
sudo launchctl load /Library/LaunchDaemons/ 

Have also removed and rejoined the network from the CLI with no changes. If anyone has ideas I would appreciate the help!

Are you sure you typed the network ID correctly? Your peers output only shows the root servers and does not show the node ID of the network controller in the list. (Fun fact, the first 10 digits of a network ID are a zerotier node ID). So I’d check the network ID first.

Also check the output of the command systemextensionctl list. If there are any network extensions listed, there’s a known incompatibility with network extensions & many other things networking related on macOS 12.1+.

Beyond that, the only other suspect would be the network router/firewall or IDS deciding to not let ZeroTier talk from this computer.

Thanks Grant. It appears that I did somehow mistype the network ID and it now works! Just out of curiosity, is there a reason you can’t paste into the network field in the GUI client?

That would be because there’s a bug :smile: There’s a fix queued up in the next release, which should be soon™

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.