Zerotierone: NODE ID: Unknown is Back

[nischkar]

Just as the title suggests.

As the previous bug, reinstalling fixes it until the next reboot of the system
and it goes back.

Furthermore, this may be the reason, the cli says
" missing authentication token and authtoken.secret not found" even though it exists in the said path.

[laduke]

Hey, can you check
C:\ProgramData\ZeroTier\One
and
C:\Users\nischkar\AppData\Local\ZeroTier\One

They should both have authtoken.secret. The UI copies it from ProgramData to the User\AppData when it starts up. It needs admin privileges to do this.

[nischkar]

It both exists.
(C:\ProgramData\ZeroTier\One)

(appdata\Local\ZeroTier\One)

I also tried to change the file permissions, but it does not fix the problem.

[glimberg]

No luck reproducing this one reliably so far. I had it happen to me on my home machine once, but it has since magically resolved itself. It appears ZeroTier was getting into a state where it was no longer listening on the TCP control port that the UI and zerotier-cli talk to, but I couldn't figure out why before it stopped happening to me.

[ecapuano]

Experiencing this issue on multiple machines as well.

[nischkar]

@ecapuano Can you tell us what you did, maybe the developers can recreate the issue with the steps you will provide.

Thank you.

[ptiemann]

I'm new to ZeroTier as of today. Installed in on a corporate laptop was able to connect from other machines and it seemed to work fine. After a reboot I see this issue, node id is unknown. If I try to join my network I get the error:
Error Joining Network: Cannnot connect to the ZeroTier Service.
The message led me to check for a ZeroTier service and found that it was set to Automatic but was not running. I started it manually and when I check now, I have a node Id. When I check ZeroTier central, it shows I'm connected. Please advise what to check or report to assist you with debugging this.

[glimberg]

Think I found & fixed this issue. https://github.com/zerotier/ZeroTierOne/commit/352ec3430f50da47132e741c4bb19ca194e324f6

Turns out that the #define in WinSock that sets the default maximum number of open sockets is the obscenely low value of 64. I bumped this up a few orders of magnitude to 1024. Fix will be in the next release.

[shyangs]

run services.msc
start ZeroTierOneService, if it is stopping.

[laduke]

Looks like this is merged

[An0nDev]

In my experience, the zerotier-cli error may be due to inadequate permissions accessing authtoken.secret on Windows. Try launching Command Prompt as administrator first. (I was able to get my node ID with zerotier-cli info)

[jymjam]

got this exact issue a while back, rebooting my PC resolved it

[BaldStrong]

About the solution of Node ID "Unknown" or Service stops automatically on Windows

In short, uninstall version 1.4.6 and install version 1.2.8.

1. Run "ZeroTier One.msi"(version 1.4.6) and select “remove”，uninstall version 1.4.6.
2. Enter this page: https://download.zerotier.com/RELEASES/1.2.8/dist/ ,download version 1.2.8, install it.
3. The zerotier one service is up and running.

[Twang1998]

run services.msc
start ZeroTierOneService, if it is stopping.

thanks!