zerotier / zerotier/ZeroTierOne

ZeroTier service not starting - stuck on "Waiting for ZeroTier service"

Open
#1,972 7 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
17.1k
Forks
2k
PR merge metrics
No merged PRs in 30d

Description

Title: ZeroTier service not starting - stuck on "Waiting for ZeroTier service"
Issue description:

I am experiencing an issue with ZeroTier on my device. When I open the application, it gets stuck on "Waiting for ZeroTier service." I am unable to connect to any networks or use ZeroTier.

Operating System:

macOS ventura 13.3 (22E252)

ZeroTier Version:

<1.10.6>

Steps to reproduce the issue:
  1. download zerotier form the webpage
    2.install the pkg on macos
  2. open it after installed
  3. click it one the bar,and it shows "Waiting for ZeroTier service"
Troubleshooting steps already taken:

Waiting for ZeroTier service

Any help in resolving this issue would be greatly appreciated. Thank you!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the installation and launch steps on macOS Ventura 13.3 with ZeroTier version 1.10.6, then inspect the macOS service startup path behind the menu-bar application's “Waiting for ZeroTier service” state. Done means the installed service starts normally and the application can connect to a network; the issue provides no named files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, macos
Domain
desktop, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.