UI Not Detecting Invalid Local Authtoken - "Waiting for ZeroTier System Service..."

[glimberg]

Adding here to make sure we don't forget to fix. "Waiting for system service" issue is caused by an invalid copy of the service authtoken in the user's home directory.

We need to detect this by catching 403 responses from the service backend & giving the user the ability to recopy the token in the tray app.

[glimberg]

Current workaround until this is fixed

macOS fix:

• Close the ZeroTier tray application
• Open a terminal and execute the following command: rm ~/Library/Application\ Support/ZeroTier/One/authtoken.secret and possibly rm ~/Library/Application\ Support/ZeroTier/authtoken.secret as well
• Reopen the ZeroTier UI application. You should be prompted for the administrator password so you can re-copy the authtoken into your user settings folder.

Windows:

• Open Explorer and type: %LOCALAPPDATA%\ZeroTier\ into the location bar.
• Remove authtoken.secret.
• If a One subfolder exists, delete authtoken.secret from there as well.

[KB8DOA]

Same problem here with Manjaro Linux 22.04
Is there no fix for Linux?

[surfboy2000]

windows环境下，问题可以解决。

The problem can be solved under Win10

[qubex22]

Current workaround until this is fixed

macOS fix:

* Close the ZeroTier tray application

* Open a terminal and execute the following command: rm ~/Library/Application\ Support/ZeroTier/One/authtoken.secret and possibly rm ~/Library/Application\ Support/ZeroTier/authtoken.secret as well

* Reopen the ZeroTier UI application. You should be prompted for the administrator password so you can re-copy the authtoken into your user settings folder.

Windows:

* Open Explorer and type: %LOCALAPPDATA%\ZeroTier\ into the location bar.

* Remove authtoken.secret.

* If a One subfolder exists, delete authtoken.secret from there as well.

This workaround doesn't work for me in W11

[1337cookie]

I wasn't able to use the GUI for about 3 years until I stumbled on a reddit thread about this. Probably made 5-6 attempts over that time. I found dozens of instances of the same unresolved behavior in many different threads. This issue is still out there.